Search merge requestshttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests2023-04-20T17:51:46Zhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/477Upgrading dependencies2023-04-20T17:51:46ZAbhay JoshiUpgrading dependencies## 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 informationM18 - Release 0.21Okoun-Ola Fabien HouetoAbhay JoshiOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/471Critical spring Security vulnerability fixes for spring-security-web2023-04-24T14:56:27ZJayesh BagulCritical spring Security vulnerability fixes for spring-security-web## 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
- [ ] 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
vulnerabilities were detected in https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/27101 and https://community.opengroup.org/osdu/platform/system/search-service/-/security/vulnerabilities/27100
Updated the changes for the non-vulnerable version.M18 - Release 0.21Jayesh Bagulsaketh somarajuJayesh Bagulhttps://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/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/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/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/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/513Upgraded mappers.2023-06-12T13:11:28ZRiabokon Stanislav(EPAM)[GCP]Upgraded mappers.## Type of change
- [ ] Bug Fix
- [x] 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
- [x] 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.22Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/509fix cURL example folding on tutorial2023-07-04T10:50:49ZNeelesh Thakurfix cURL example folding on tutorialFix cURL example folding on tutorial. Complete tutorial is not visible otherwise.Fix cURL example folding on tutorial. Complete tutorial is not visible otherwise.M19 - Release 0.22https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/507add more example to search tutorial2023-07-04T10:51:12ZNeelesh Thakuradd more example to search tutorialfurther improvement to search tutorial
- exist query
- adds more examplefurther improvement to search tutorial
- exist query
- adds more exampleM19 - Release 0.22https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/553Cherry-pick 'Enable highlighting results' into release/0.232023-09-01T15:47:55ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Enable highlighting results' into release/0.23**Original MR**: !541
### 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**: !541
### 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-541)M20 - Release 0.23David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/552Upgrade First Party Library Dependencies for Release 0.232023-09-05T07:45:00ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.23This 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: aa6694df6f10f4a52ae4881a8d2269f7d17071e2
Maven: 0.24.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.23.0-rc2 | 0.23.0-rc2 |
| 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
SHA: 7b3a60ffc512521cf7b1536569ad8e073bff307c
Maven: 0.24.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.23.1 | 0.23.1 |
| 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 |M20 - Release 0.23https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/551Cherry-pick: Merge branch 'fix-sort-test' into 'master'2023-08-29T11:36:00ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comCherry-pick: Merge branch 'fix-sort-test' into 'master'Cherry-pick from https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/550
## Type of change
- [ ] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
##...Cherry-pick from https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/550
## 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 informationM20 - Release 0.23Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/550Switch tests to common and updated sort model2023-08-29T07:50:02ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comSwitch tests to common and updated sort model
## 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 prov...
## 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] Common code
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
The custom model in a testing directory is not aligned with the updated model from core-common, making the sort test with filter fail.
## What is the new/expected behavior?
The common model works fine, and the request with the new filter property formed as expected.M20 - Release 0.23Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/546Revert "Merge branch 'GONRG-7560-policy-update' into 'master'"2023-09-05T08:06:10ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRevert "Merge branch 'GONRG-7560-policy-update' 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
- [ ] 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 informationM20 - Release 0.23https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/544GONRG-7560: update policy in the service2023-08-24T10:19:21ZYauheni Rykhter (EPAM)GONRG-7560: update policy in the serviceM20 - Release 0.23Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/543Exclude system/metadata indices in searches with wildcard kind2023-09-04T07:33:32ZZhibin MaiExclude system/metadata indices in searches with wildcard kind## Type of change
- [ ] Bug Fix
- [x] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES]
## Does this introduce a change in the cloud prov...## Type of change
- [ ] Bug Fix
- [x] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
## Does this introduce a change in the core logic?
- [YES]
## 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?
- [NO]
## What is the current behavior?
In searches with wildcard kind, only the ElasticSearch system/internal indices started with dot will be excluded.
## What is the new/expected behavior?
In searches with wildcard kind, the ElasticSearch system/internal indices started with dot and the indices with authority as "system-meta-data" will be excluded.
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful information
- ADR [ADR: Exclude indices of the system/meta data from the search results unless the indices (kinds) of the system/meta data are explicitly specified in the search query](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/131)
- OSDU data-definitions
- [6.1.2 Record kind](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/06-LifecycleProperties.md#612-record-kind)
- [Appendix D.1.3 Schema Identifier `kind` Limitations](https://community.opengroup.org/osdu/data/data-definitions/-/blob/master/Guides/Chapters/93-OSDU-Schemas.md#appendix-d13-schema-identifier-kind-limitations)
-M20 - Release 0.23Thomas Gehrmann [slb]Zhibin MaiThomas Gehrmann [slb]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/542AWS Merge Dev Into Master2023-08-24T11:59:29ZGuillaume CailletAWS Merge Dev Into MasterM20 - Release 0.23Guillaume CailletGuillaume Caillet