Search merge requestshttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests2023-07-18T07:06:54Zhttps://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/532JDK 17 migration (GONRG-7477)2024-01-25T13:47:32ZYurii Ruban [EPAM / GCP]JDK 17 migration (GONRG-7477)# Description:
Migration from Java 8 to Java 17.
# How to test:
Via Unit and Integration tests.
# Changes include:
- [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:...# Description:
Migration from Java 8 to Java 17.
# How to test:
Via Unit and Integration tests.
# Changes include:
- [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [ ] Common code
# Dev Checklist:
- [ ] Added Unit Tests, wherever applicable.
- [ ] Updated the Readme, if applicable.
- [ ] Existing Tests pass
- [ ] Verified functionality locally
- [ ] Self Reviewed my code for formatting and complex business logic.
# Other comments:
* Upgraded 'lombok' & 'jacoco' plugin version
* Changed TestRunner 'PowerMockRunner' to 'MockitoJUnitRunner'
* Removed 'powermock-api-mockito2' & 'powermock-module-junit4' dependenciesM20 - Release 0.23Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/531Cherry-pick 'spring-security-core upgrade' into release/0.222023-07-13T13:25:55ZChad LeongCherry-pick 'spring-security-core upgrade' into release/0.22**Original MR**: !530
### 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**: !530
### 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-530)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/530spring-security-core upgrade2023-07-13T09:13:54Zsagar thapaspring-security-core upgrade# Issue links: -
https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/28318 - AWS
https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/28316 - IBM
http...# Issue links: -
https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/28318 - AWS
https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/28316 - IBM
https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/28317 - search-core
## spring-security-core upgrade affects following cloud provider.
- [x] AWS
- [ ] Azure
- [ ] Google Cloud
- [x] IBM
# Additional information
common core **spring-security-core** is also upgraded as per the vulnerability scan report.M19 - Release 0.22sagar thapasagar thapahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/529tomcat upgrade2023-07-05T10:49:19ZHarshika Dhoottomcat upgrade## 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 informationHarshika DhootHarshika Dhoothttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/528tomcat upgraded2023-07-05T07:08:09ZHarshika Dhoottomcat upgraded## 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...## 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]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/527Add Documentation for Azure specific limitation2023-07-04T11:01:21ZThulasi Dass SubramanianAdd Documentation for Azure specific limitation- Issue: https://community.opengroup.org/osdu/platform/system/search-service/-/issues/103
- added Documentation for Azure specific Http Header size limitation- Issue: https://community.opengroup.org/osdu/platform/system/search-service/-/issues/103
- added Documentation for Azure specific Http Header size limitationM19 - Release 0.22Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/526Tomcat vuln fixed component governance2023-07-03T12:13:47ZHarshika DhootTomcat vuln fixed component governance## 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 clou...## 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] NO
## What is the current behavior?
## What is the new/expected behavior? Vulnerability for tomcat to be fixed
## Have you added/updated Unit Tests and Integration Tests? NO
## Any other useful information
https://dev.azure.com/OpenEnergyPlatform/Open%20Energy%20Platform/_componentGovernance/oep-deployment-resources/alert/7921145?typeId=13890738&pipelinesTrackingFilter=0Harshika DhootHarshika Dhoothttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/525GONRG-7392: use non-root user for images2023-06-30T12:30:14ZYauheni Rykhter (EPAM)GONRG-7392: use non-root user for images## 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
- [x] 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 informationM19 - Release 0.22Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/524Add global variable limitsEnabled (GONRG-7266)2023-06-27T07:29:40ZAndrei Skorkin [EPAM / GCP]Add global variable limitsEnabled (GONRG-7266)## 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?
- [ ] AWS
- [ ] Azure
- [x] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM19 - Release 0.22Andrei Skorkin [EPAM / GCP]Andrei Skorkin [EPAM / GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/523Fix for a sporadic IT failure2023-08-25T22:30:13ZSabarish 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/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/521Component governance build failure vulnerabilities fixed2023-07-04T10:40:13ZHarshika DhootComponent governance build failure vulnerabilities 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 clou...## 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 information
https://dev.azure.com/OpenEnergyPlatform/Open%20Energy%20Platform/_componentGovernance/oep-deployment-resources/alert/7921145?typeId=13890738&pipelinesTrackingFilter=0M19 - Release 0.22Harshika DhootHarshika Dhoothttps://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/519The kind's alias uses hashCode() function that sometimes returns negative...2023-06-20T05:08:13ZSabarish 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?
## What is the new/expected behavior?
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful information
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.https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/518elasticsearchcred using vmcache2023-07-13T15:28:05ZAkanksha Prasadelasticsearchcred using vmcache## 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/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/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/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/514Vulnerability Fix for search2023-06-19T07:38:20ZKamalika SahaVulnerability Fix for search## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] Vulnerability Fix
**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 c...## Type of change
- [ ] Bug Fix
- [ ] Feature
- [x] Vulnerability Fix
**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?
- [ ] AWS
- [x] Azure
- [ ] Google Cloud
- [ ] IBM
## Does this introduce a breaking change?
- [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 Saha