Search merge requestshttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests2023-08-19T08:54:42Zhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/426Verify integration test2023-08-19T08:54:42ZZhibin MaiVerify integration test## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud p...## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationZhibin MaiZhibin Maihttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/533Upgrade First Party Library Dependencies for Release 0.222023-07-18T07:06:54ZChad LeongUpgrade First Party Library Dependencies for Release 0.22This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated.
Furthermore, the upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: db0304252cb5708aee16125a4f34f7b04bd38fb7
Maven: 0.23.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ----------------------------------------------------- | -------------------------- | -------------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.13.0-rc6 |
| core-lib-gc | 0.21.0 | |
| os-core-lib-aws | 0.21.0 | 0.21.0 |
| os-core-common | 0.20.0-rc1, 0.19.0, 0.21.0 | 0.19.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-3
SHA: d40ac663270134d4572e877d2b1518ddc635877f
Maven: 0.23.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ----------------------------------------------------- | -------------------------- | -------------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.13.0-rc6 |
| core-lib-gc | 0.22.1 | |
| os-core-lib-aws | 0.22.0 | 0.22.0 |
| os-core-common | 0.20.0-rc1, 0.19.0, 0.22.0 | 0.19.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26 |M19 - Release 0.22https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/517Draft: enabling vm cache for elasticsearchcred2023-06-28T06:39:43ZAkanksha PrasadDraft: enabling vm cache for elasticsearchcred## Type of change
- [yes] Bug Fix
- [no] Feature
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [YES] Azure
## Does this introduc...## Type of change
- [yes] Bug Fix
- [no] Feature
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [YES] Azure
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
ElasticSearch Cred is fetched from redis cache which was causing during update of elastic search primary user secret as 500 ,internal server error.This was majorly because,refresh time of redis is 60 minutes.Hence,in that duration 500 status code was returned
## What is the new/expected behavior?
After the duration of secret rotation completed,search should return 200 success status code
## Have you added/updated Unit Tests and Integration Tests?
yes
## Any other useful informationAkanksha PrasadAkanksha Prasadhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/520component governance build failure fixed2023-06-27T06:34:52ZHarshika Dhootcomponent governance build failure fixed## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
- NO
## Does this introduce a change in the cl...## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
- NO
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [X] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationHarshika DhootHarshika Dhoothttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/522The kind's alias uses hashCode() function that sometimes returns negative...2023-06-20T07:20:19ZSabarish K R EThe kind's alias uses hashCode() function that sometimes returns negative...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] IT Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] NO
## Does this introduce a chang...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] IT Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] NO
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
One of the MultiKindsValidator test cases fails with an error from search service indicating that the length exceeds 3840 bytes.
This happens because, in the IT, we assume that the hashCode() function used in finding out the Index Alias, always returns positive numbers. So, this case fails when the hashCode() results in negative numbers as the "-" causes the length of the index to increase beyond 3840.
## What is the new/expected behavior?
Modified IT to account for the negative hashCode()
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful information
The kind's alias uses hashCode() function that sometimes returns negative numbers. The test does not account for the extra character occupied by the - symbol, when the hashCode is used for the construction of index alias namehttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/515Fix for a sporadic IT failure2023-06-20T07:18:21ZSabarish K R EFix for a sporadic IT failure## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] IT Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] NO
## Does this introduce a chang...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] IT Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] NO
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
One of the MultiKindsValidator test cases fails with an error from search service indicating that the length exceeds 3840 bytes.
This happens because, in the IT, we assume that the hashCode() function used in finding out the Index Alias, always returns positive numbers. So, this case fails when the hashCode() results in negative numbers as the "-" causes the length of the index to increase beyond 3840.
## What is the new/expected behavior?
Modified IT to account for the negative hashCode()
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful information
The kind's alias uses hashCode() function that sometimes returns negative numbers. The test does not account for the extra character occupied by the - symbol, when the hashCode is used for the construction of index alias namehttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/516Fix for a sporadic IT failure2023-06-20T05:06:06ZSabarish K R EFix for a sporadic IT failure## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] IT Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] NO
## Does this introduce a chang...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] IT Fix
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO] NO
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
One of the MultiKindsValidator test cases fails with an error from search service indicating that the length exceeds 3840 bytes.
This happens because, in the IT, we assume that the hashCode() function used in finding out the Index Alias, always returns positive numbers. So, this case fails when the hashCode() results in negative numbers as the "-" causes the length of the index to increase beyond 3840.
## What is the new/expected behavior?
Modified IT to account for the negative hashCode()
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful information
The kind's alias uses hashCode() function that sometimes returns negative numbers. The test does not account for the extra character occupied by the - symbol, when the hashCode is used for the construction of index alias namehttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/482Full Upgrade of First Party Library Dependencies for Release 0.202023-05-22T15:40:41ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.20This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will ...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will often fail, since the upgrades were previously rejected for failing pipelines and have not been directly addressed yet.
This upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
This MR may co-exist with a separate, smaller upgrade MR.
If both pass, this one should be used instead.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: f702c5b2dbdc62ccc66d1b8177510493c56fb7df
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ----------------------------------------------------- | ------------------ | -------------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0-rc3 | |
| os-core-lib-aws | 0.21.0-rc1 | 0.21.0-rc1 |
| obm | 0.18.0 | |
| oqm | 0.18.0 | |
| os-core-common | 0.20.0-rc1, 0.19.0 | 0.19.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.18.0 | |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.yaml.snakeyaml | 1.33 | 1.26 |
```
Critical: Found Vulnerable Snake YAML dependency (<2.0)
├─ _Root_
│ ├─ org.projectlombok.lombok == 1.18.8
│ │ └─ org.opengroup.osdu.os-core-common == 0.20.0-rc1
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.6.6
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-core == 0.21.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-security == 2.7.7
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-byoc == 0.21.0-SNAPSHOT
│ │ └─ pl.allegro.tech.embedded-elasticsearch == 2.10.0
│ │ └─ com.fasterxml.jackson.dataformat.jackson-dataformat-yaml == 2.14.1
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-gc == 0.21.0-SNAPSHOT
│ │ └─ org.elasticsearch.elasticsearch == 7.8.1
│ │ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-aws == 0.21.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-security == 2.7.7
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-azure == 0.21.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.core-lib-azure == 0.20.0-rc5
│ │ └─ org.redisson.redisson == 3.15.3
│ │ └─ org.yaml.snakeyaml == 1.33
│ └─ org.opengroup.osdu.search-ibm == 0.21.0-SNAPSHOT
│ └─ org.yaml.snakeyaml == 1.33
└─ testing/integration-tests/
├─ org.opengroup.osdu.search.search-test-core == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
├─ org.opengroup.osdu.search.search-test-aws == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
├─ org.opengroup.osdu.search.search-test-azure == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
├─ org.opengroup.osdu.search.search-test-gc == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
├─ org.opengroup.osdu.search.search-test-ibm == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
└─ org.opengroup.osdu.search.search-test-anthos == 0.21.0-SNAPSHOT
└─ org.elasticsearch.elasticsearch == 7.8.1
└─ org.elasticsearch.elasticsearch-x-content == 7.8.1
└─ org.yaml.snakeyaml == 1.26
```
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-2
SHA: f0dded7025b346166af1015cd2cd7bebc050f8a4
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| --------------------------------------------------- | ---------- | -------------------------- |
| core-lib-azure | 0.20.0 | 0.20.0 |
| core-lib-gc | 0.20.0 | |
| os-core-lib-aws | 0.21.0-rc2 | 0.21.0-rc2 |
| obm | 0.20.0 | |
| oqm | 0.20.0 | |
| os-core-common | 0.20.1 | 0.20.1 |
| os-core-lib-ibm | 0.20.0 | 0.20.0 |
| osm | 0.20.0 | |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.yaml.snakeyaml | 1.33 | 1.26, 1.27, 2.0 |
```
Critical: Found Vulnerable Snake YAML dependency (<2.0)
├─ _Root_
│ ├─ org.projectlombok.lombok == 1.18.8
│ │ └─ org.opengroup.osdu.os-core-common == 0.20.1
│ │ └─ org.springframework.boot.spring-boot-starter-web == 2.6.6
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-core == 0.21.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-security == 2.7.7
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-byoc == 0.21.0-SNAPSHOT
│ │ └─ pl.allegro.tech.embedded-elasticsearch == 2.10.0
│ │ └─ com.fasterxml.jackson.dataformat.jackson-dataformat-yaml == 2.14.1
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-gc == 0.21.0-SNAPSHOT
│ │ └─ org.elasticsearch.elasticsearch == 7.8.1
│ │ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-aws == 0.21.0-SNAPSHOT
│ │ └─ org.springframework.boot.spring-boot-starter-security == 2.7.7
│ │ └─ org.springframework.boot.spring-boot-starter == 2.7.7
│ │ └─ org.yaml.snakeyaml == 1.33
│ ├─ org.opengroup.osdu.search-azure == 0.21.0-SNAPSHOT
│ │ └─ org.opengroup.osdu.core-lib-azure == 0.20.0
│ │ └─ org.redisson.redisson == 3.15.3
│ │ └─ org.yaml.snakeyaml == 1.33
│ └─ org.opengroup.osdu.search-ibm == 0.21.0-SNAPSHOT
│ └─ org.yaml.snakeyaml == 1.33
└─ testing/integration-tests/
├─ org.opengroup.osdu.search.search-test-core == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
├─ org.opengroup.osdu.search.search-test-aws == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
├─ org.opengroup.osdu.search.search-test-azure == 0.21.0-SNAPSHOT
│ └─ org.opengroup.osdu.core-lib-azure == 0.20.0
│ └─ org.redisson.redisson == 3.15.3
│ └─ org.yaml.snakeyaml == 1.27
├─ org.opengroup.osdu.search.search-test-gc == 0.21.0-SNAPSHOT
│ └─ org.elasticsearch.elasticsearch == 7.8.1
│ └─ org.elasticsearch.elasticsearch-x-content == 7.8.1
│ └─ org.yaml.snakeyaml == 1.26
└─ org.opengroup.osdu.search.search-test-anthos == 0.21.0-SNAPSHOT
└─ org.elasticsearch.elasticsearch == 7.8.1
└─ org.elasticsearch.elasticsearch-x-content == 7.8.1
└─ org.yaml.snakeyaml == 1.26
```M18 - Release 0.21Yauhen Shaliou [EPAM/GCP]Yauhen Shaliou [EPAM/GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/494Set FailOnError to false2023-05-22T15:17:46ZYash DholakiaSet FailOnError to false## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provi...## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [X] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Dependency-check-maven fails when nvd.nist is down and eventually build fails.
## What is the new/expected behavior?
Build will not fail when Dependency-check-maven fails
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM18 - Release 0.21Yash DholakiaYash Dholakiahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/374Increasing Tomcat.maxthread to 4002023-05-13T05:07:54ZAkanksha PrasadIncreasing Tomcat.maxthread to 400## Type of change
- [ yes] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
This change is done so that we can increase rps without getting 503
## Does this introduce a change in the...## Type of change
- [ yes] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
This change is done so that we can increase rps without getting 503
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [yes ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO] no
## What is the current behavior?
Currently it is enabled for 200 tomcat.server.maxthread and rps is 30 rps
## What is the new/expected behavior?
In new behaviour,increasing the tomcat.server.maxthread to 400 will increase rps and less 503
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationAkanksha PrasadAkanksha Prasadhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/486Draft: Merge branch 'azure/cherrypick-m14-m16' into 'azure/cherrypick-m14-m16'2023-04-13T02:02:21ZOsborn ChenDraft: Merge branch 'azure/cherrypick-m14-m16' into 'azure/cherrypick-m14-m16'## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud p...## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/457Draft: Vulnerability Fix for Search Service2023-04-04T09:43:07ZKamalika SahaDraft: Vulnerability Fix for Search Service## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud p...## Type of change
- [x] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationKamalika SahaKamalika Sahahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/469optimize geo queries: remove redundant call and use filter2023-03-23T23:22:48ZNeelesh Thakuroptimize geo queries: remove redundant call and use filter- We make one extra query to retrieve field types when we have geo filter supplied on requests. This was required as same name attribute across different kinds can be of geo-point or geo-shape. This can be removed as Elasticsearch apis (...- We make one extra query to retrieve field types when we have geo filter supplied on requests. This was required as same name attribute across different kinds can be of geo-point or geo-shape. This can be removed as Elasticsearch apis (>=v7.11) handle it in API.
- Enable Elasticsearch native caching by using filters on geo queries
## Type of change
- [X] Bug Fix
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [X] Azure
## Does this introduce a breaking change?
- [NO]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/464Return records that belong to the target data partition id.2023-03-20T22:22:28ZMorris EstepaReturn records that belong to the target data partition id.## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/system/search-service/-/issues/110
## Does this introduce a cha...## Type of change
- [X] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
https://community.opengroup.org/osdu/platform/system/search-service/-/issues/110
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [X] AWS
- [ ] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
Records from other data partition ids in AWS are getting returned to the user
## What is the new/expected behavior?
Only records from the user's data partition id are returned.
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful informationM16 - Release 0.19Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/441Cherry-pick 'Fix issue where users could not search using hundreds of kinds a...2023-02-21T17:42:08ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Fix issue where users could not search using hundreds of kinds at once' into release/0.19**Original MR**: !440
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporati...**Original MR**: !440
### This MR is a Cherry Pick into a Release Branch.
After the release branch is first created, any subsequent changes use this process to update the release (often resulting in a new patch tag) without incorporating all changes in the default branch.
These MRs must be approved by the PMC before they are merged, since they alter the scope of the release.
To see more details about the change itself, look at the Original MR listed above.
#### Skipped Pipeline
Normally, pipelines are not executed on the cherry pick branch/MR prior to merging.
This optimization is accepted because the code was tested when it merged into the default branch, and will be tested again in the release branch prior to tagging.
However, if anybody feels that the MR requires further scrutiny -- whether because it had conflicts in the cherry-picking, it interfaces with some drastically altered logic between the branches, or any other reason -- we can run the pipeline here prior to merging.
#### If There's Reason to Run a Pipeline
If you want to see a pipeline result before this merges, first add a comment explaining why you'd like to see the pipeline results so the PMC and others know your thinking.
Then, mark the MR as a Draft MR (using the vertical ellipsis above, choose 'Mark as Draft').
This prevents the MR from being approved & merged accidentally by a busy release coordinator who didn't see your comment.
Finally, if you are a maintainer on the project, launch a pipeline on this branch.
Since this branch is a protected branch and the MR has ~no-detached-pipeline set, all integration tests will run and there's no need for any `trusted-*` branches.
[Launch a Pipeline for this Branch](https://community.opengroup.org/osdu/platform/system/search-service/-/pipelines/new?ref=cherry-pick-for-440)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/427Upgrade First Party Library Dependencies for Release 0.192023-02-18T07:31:16ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.19This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any...This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability.
However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated.
Furthermore, the upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: e136c36ae0f5b25769df441fb839a3c9a194b7a0
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------- | -------------------------- | -------------------------- |
| core-lib-azure | 0.17.0 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0-rc3 | |
| os-core-lib-aws | 0.18.0 | 0.14.0-rc2 |
| obm | 0.18.0 | |
| oqm | 0.18.0 | |
| os-core-common | 0.18.0, 0.17.0, 0.19.0-rc6 | 0.18.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.18.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.22 | 5.3.22 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-3
SHA: bf7c0771f00f76ec7699f810168a2417a8dcdb47
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/integration-tests/ |
| ------------------------------------------------------- | -------------- | -------------------------- |
| core-lib-azure | 0.17.0 | 0.13.0-rc6 |
| core-lib-gcp | 0.19.0 | |
| os-core-lib-aws | 0.19.0 | 0.14.0-rc2 |
| obm | 0.19.0 | |
| oqm | 0.19.0 | |
| os-core-common | 0.19.0, 0.17.0 | 0.19.0 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
| osm | 0.19.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.2.2 | 2.13.2.2 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.17.1 | 2.11.2 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.24, 5.3.22 | 5.3.22 |M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/406Vulnerability fix ibm search service2023-02-16T13:37:44ZPintu GuptaVulnerability fix ibm search serviceFollowing CVE has been fix with this MR :
| cve | link |
|----------------|-------------------------------------------------|
| CVE-2022-25857 | https://nvd.nist.gov/vuln/detail/CVE-2...Following CVE has been fix with this MR :
| cve | link |
|----------------|-------------------------------------------------|
| CVE-2022-25857 | https://nvd.nist.gov/vuln/detail/CVE-2022-25857 |
| CVE-2022-42003 | https://nvd.nist.gov/vuln/detail/CVE-2022-42003 |
| CVE-2022-42004 | https://nvd.nist.gov/vuln/detail/CVE-2022-42004 |
| CVE-2021-36090 | https://nvd.nist.gov/vuln/detail/CVE-2021-36090 |
| CVE-2022-42252 | https://nvd.nist.gov/vuln/detail/CVE-2022-42252 |Pintu GuptaPintu Guptahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/428Adding support for EKS 1.232023-02-10T18:11:19ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/257Updated search service to use RedisAzureCache2023-02-04T05:36:24ZShiv SinghUpdated search service to use RedisAzureCacheCherry-picking MR to azure/m10-master: https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/251Cherry-picking MR to azure/m10-master: https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/251Shiv SinghShiv Singhhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/306Merge branch 'upgrade-dependencies' into 'master'2023-02-04T05:36:21ZHarsheet ShahMerge branch 'upgrade-dependencies' into 'master'## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud p...## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES/NO]
## Does this introduce a change in the cloud provider implementation, if so which cloud?
- [ ] AWS
- [ ] Azure
- [ ] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [YES/NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationHarsheet ShahHarsheet Shah