Search merge requestshttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests2023-06-12T13:11:28Zhttps://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/512Cherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into ...2023-05-31T07:55:34ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Upgrade First Party Library Dependencies for Release 0.21' into release/0.21**Original MR**: !511
### 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**: !511
### 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-511)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/511Upgrade First Party Library Dependencies for Release 0.212023-05-30T23:41:48ZDavid Diederichd.diederich@opengroup.orgUpgrade First Party Library Dependencies for Release 0.21This 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: 1db3d0f8882fbf31828c101ae2506312cc50f912
Maven: 0.22.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-rc5 | 0.21.0-rc5 |
| 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 | 2.0 | 1.26 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 30833ba57cff023808993b6948e9cf93b7b7f9ac
Maven: 0.22.0-SNAPSHOT
```
| Maven Dependencies | testing/integration-tests/ | _Root_ |
| ----------------------------------------------------- | -------------------------- | ------------------ |
| core-lib-azure | 0.13.0-rc6 | |
| os-core-lib-aws | 0.21.0 | |
| os-core-common | 0.19.0 | 0.20.0-rc1, 0.19.0 |
| os-core-lib-ibm | 0.15.2 | |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.11.1, 2.13.3 | 2.17.1 |
| (3rd Party) org.apache.logging.log4j.log4j-core | 2.13.3 | |
| (3rd Party) org.apache.logging.log4j.log4j-jul | 2.13.3 | |
| (3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.13.3 | |
| (3rd Party) org.apache.logging.log4j.log4j-to-slf4j | 2.11.2 | 2.17.1 |
| (3rd Party) org.yaml.snakeyaml | 1.26 | 2.0 |M18 - Release 0.21https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/510Cherry-pick 'Search not handling Policy error responses gracefully (GONRG-710...2023-05-24T10:04:24ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Search not handling Policy error responses gracefully (GONRG-7105)' into release/0.21**Original MR**: !505
### 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**: !505
### 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-505)M18 - Release 0.21David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://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/508Fixing variable for aws2023-05-19T22:07:51ZAbhay JoshiFixing variable for aws## 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?
- [ X] AWS
- [ ] 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 informationM18 - Release 0.21Abhay JoshiYong ZengMadalyn MarabellaAbhay Joshihttps://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/506Update images for OpenJDK2023-05-19T14:05:15ZOrest Khud [EPAMĀ / GCP]Update images for OpenJDK## 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.21https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/505Search not handling Policy error responses gracefully (GONRG-7105)2023-10-26T03:39:58ZRiabokon Stanislav(EPAM)[GCP]Search not handling Policy error responses gracefully (GONRG-7105)## Type of change
- [X] Bug Fix
- [ ] 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?
- [x] AWS
- [x] Azure
- [x] Google Clou...## Type of change
- [X] Bug Fix
- [ ] 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?
- [x] AWS
- [x] Azure
- [x] Google Cloud
- [x] IBM
## Does this introduce a breaking change?
- [YES]
## What is the new/expected behavior?
A new response from Search Service, when we have an exception from Policy Service.
Please, I would like to pay your attention to this screenshot.
![Screenshot_2023-05-19_at_13.41.12](/uploads/cc27cbb056c425fa50aaa474de408f8a/Screenshot_2023-05-19_at_13.41.12.png)M18 - Release 0.21Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/504UserAgent changes2023-05-12T17:33:46ZAbhay JoshiUserAgent changes## 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]
No
## Does this introduce a change in the clou...## 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]
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?
- [YES/NO]
No
## What is the current behavior?
## What is the new/expected behavior?
API for aws can be tracked
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationM18 - Release 0.21Okoun-Ola Fabien HouetoAbhay JoshiYong ZengOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/503cleanup and enhance documentation2023-05-15T11:55:56ZNeelesh Thakurcleanup and enhance documentation- General improvement on indexer/search service's minor enhancements
- Update request samples to match stable OSDU schema properties/kinds
- Add documentation for common discovery via VirtualProperties
- Add documentation for Intersectin...- General improvement on indexer/search service's minor enhancements
- Update request samples to match stable OSDU schema properties/kinds
- Add documentation for common discovery via VirtualProperties
- Add documentation for Intersecting Geo polygon query
- Add documentation on precise match
- Add documentation for special text searches: query by null or empty values etc.
- Remove old architecture diagrams which are not valid anymore (Imported during DES migration)
## Type of change
- [X] DocumentationM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/502fixing snake yaml vulnarability2023-05-11T23:41:22ZKiran Veerapanenifixing snake yaml vulnarabilityhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/501update NOTICE file2023-05-11T17:04:26ZMadalyn Marabellaupdate NOTICE file## 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.21Madalyn MarabellaMadalyn Marabellahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/500base image changed2023-05-12T14:43:11ZOrest Khud [EPAMĀ / GCP]base image changed## 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.21https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/499Add space flexibility for nested queries2023-05-19T15:41:55Zsaketh somarajuAdd space flexibility for nested queries## Type of change
- [Yes] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
[Search service issue 65](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/65)
...## Type of change
- [Yes] Bug Fix
- [ ] Feature
**Please provide link to gitlab issue or ADR(Architecture Decision Record)**
[Search service issue 65](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/65)
## Does this introduce a change in the core logic?
- [NO]
## Does this introduce a breaking change?
- [NO]
## What is the current behavior?
- Space should be present between , and ( for nested search
- Space should not be present between "d" of nested and (
## What is the new/expected behavior?
The query should be parsed irrespective of spaces.
## Have you added/updated Unit Tests and Integration Tests?
Yes
## Any other useful informationM18 - Release 0.21saketh somarajusaketh somarajuhttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/498GONRG-7029: update anthos to baremetal2023-05-19T08:46:29ZYauheni Rykhter (EPAM)GONRG-7029: update anthos to baremetalM18 - Release 0.21Yauheni Rykhter (EPAM)Yauheni Rykhter (EPAM)https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/497M18 service and CICD updates2023-05-09T19:10:28ZMadalyn MarabellaM18 service and CICD updatesAWS code updates only
## 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 ...AWS code updates only
## 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.21Madalyn MarabellaMadalyn Marabellahttps://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/496Renamed domain env variable (GONRG-6912)2023-05-17T09:05:47ZYurii Ruban [EPAM / GCP]Renamed domain env variable (GONRG-6912)# Description:
Renamed the domain environment variable to group id for a better understanding of the origin of the variables
# How to test:
Check unit and int tests.
# Changes include:
- [x] Refactor (a non-breaking change that impro...# Description:
Renamed the domain environment variable to group id for a better understanding of the origin of the variables
# How to test:
Check unit and int tests.
# Changes include:
- [x] Refactor (a non-breaking change that improves code maintainability).
# Changes in:
- [x] GCPM18 - Release 0.21Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/search-service/-/merge_requests/495Draft: Gonrg 6943 test branch2023-12-08T15:22:36ZAliaksandr Ramanovich (EPAM)Draft: Gonrg 6943 test branchTEST MR do NOT mergeTEST MR do NOT mergeAliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)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 Dholakia