Indexer merge requestshttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests2023-02-17T20:35:45Zhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/489Security fixes AWS2023-02-17T20:35:45ZYash DholakiaSecurity fixes AWScommit bbcc6995
Author: Abhay <bios@amazon.com>
Date: Fri Dec 02 2022 10:44:20 GMT-0800 (Pacific Standard Time)
upgrade dependenciescommit bbcc6995
Author: Abhay <bios@amazon.com>
Date: Fri Dec 02 2022 10:44:20 GMT-0800 (Pacific Standard Time)
upgrade dependenciesM16 - Release 0.19Yash DholakiaYash Dholakiahttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/484Cherry-pick 'Create index alias when index is created' into release/0.192023-02-14T07:38:30ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Create index alias when index is created' into release/0.19**Original MR**: !468
### 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**: !468
### 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/indexer-service/-/pipelines/new?ref=cherry-pick-for-468)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/483Cherry-pick 'adding support for EKS 1.23' into release/0.192023-02-11T01:58:24ZMarc Burnie [AWS]Cherry-pick 'adding support for EKS 1.23' into release/0.19Adding support for EKS 1.23
Original MR: osdu/platform/system/indexer-service!481
(cherry picked from commit e8a23c6b26c23115437b8be3843c15af7510e705)
Only AWS Helm Chart changesAdding support for EKS 1.23
Original MR: osdu/platform/system/indexer-service!481
(cherry picked from commit e8a23c6b26c23115437b8be3843c15af7510e705)
Only AWS Helm Chart changesM16 - Release 0.19David Diederichd.diederich@opengroup.orgMarc Burnie [AWS]David Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/482adding support for EKS 1.232023-02-14T13:30:15ZMarc Burnie [AWS]adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/481Adding support for EKS 1.232023-02-10T21:26:36ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/478Adding support for EKS 1.232023-02-10T18:25:47ZMarc Burnie [AWS]Adding support for EKS 1.23M16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/476Cherry-pick 'Adding retry for 502 and 503 bad gateway error' into release/0.192023-02-11T02:16:32ZDavid Diederichd.diederich@opengroup.orgCherry-pick 'Adding retry for 502 and 503 bad gateway error' into release/0.19**Original MR**: !450
### 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**: !450
### 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/indexer-service/-/pipelines/new?ref=cherry-pick-for-450)M16 - Release 0.19David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/475Upgrade First Party Library Dependencies for Release 0.192023-02-18T07:29:31ZDavid 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: 7e05ff57468b77ec2a561c367bb803b7e30c7dcd
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | ---------------------- |
| core-lib-azure | 0.18.0-rc3 | 0.12.0-rc10 |
| core-lib-gcp | 0.19.0-rc7 | |
| os-core-lib-aws | 0.18.0 | 0.14.0-rc2 |
| obm | 0.19.0-rc4 | |
| oqm | 0.19.0-rc4 | |
| os-core-common | 0.16.1, 0.19.0-rc3 | 0.14.0-rc8 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.13.0 |
| osm | 0.18.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.4.2, 2.13.2.2, 2.13.4 | 2.13.2.2, 2.13.2 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.4.6 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.11.2, 2.13.0 |
| (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-to-slf4j | 2.17.1 | 2.11.2, 2.13.0 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.22 | 5.3.23 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-3
SHA: dd77a963605e78cd0f8d2dcbda5f6ab0b79d4b6e
Maven: 0.20.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | ---------------------- |
| core-lib-azure | 0.18.0-rc3 | 0.12.0-rc10 |
| 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.16.1, 0.19.0 | 0.14.0-rc8 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.13.0 |
| osm | 0.19.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.13.4.2, 2.13.2.2, 2.13.4 | 2.13.2.2, 2.13.2 |
| (3rd Party) net.minidev.json-smart | 2.4.7 | 2.4.6 |
| (3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.11.1, 2.11.2, 2.13.0 |
| (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-to-slf4j | 2.17.1 | 2.11.2, 2.13.0 |
| (3rd Party) org.springframework.spring-webflux | 5.3.22 | |
| (3rd Party) org.springframework.spring-webmvc | 5.3.22 | 5.3.23 |M16 - Release 0.19https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/472Updated bean creation (GONRG-6346)2023-02-06T15:23:30ZYurii Ruban [EPAM / GCP]Updated bean creation (GONRG-6346)# Description:
Updated bean creation
# How to test:
Check info endpoint
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [x] Bugfix (a non-breaking change that solves an issue).
- [ ] Ne...# Description:
Updated bean creation
# How to test:
Check info endpoint
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [x] Bugfix (a non-breaking change that solves an issue).
- [ ] New feature (a non-breaking change that adds functionality).
- [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [x] GCP
- [ ] Azure
- [ ] AWS
- [ ] IBM
# Dev Checklist:
- [x] Added Unit Tests, wherever applicable.
- [x] Updated the Readme, if applicable.
- [x] Existing Tests pass
- [x] Verified functionality locally
- [x] Self Reviewed my code for formatting and complex business logic.M16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/471minor log fix2023-02-01T14:19:08ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comminor log fixfix logs for event processing.fix logs for event processing.M16 - Release 0.19Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/470Gc rework consumers2023-01-31T19:18:52ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comGc rework consumers# Description:
- Rework of consumers, redundant serialization\deserialization thrown away.
- Utilized subscriber throughput configuration added to OQM.
- Fixed major memory leak related to misconfigured spring scope.
# How to test:
Doe...# Description:
- Rework of consumers, redundant serialization\deserialization thrown away.
- Utilized subscriber throughput configuration added to OQM.
- Fixed major memory leak related to misconfigured spring scope.
# How to test:
Does functionality was tested and how?
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
- [ ] Bugfix (a non-breaking change that solves an issue).
- [x] New feature (a non-breaking change that adds functionality).
- [ ] Breaking change (a change that is not backward-compatible and/or changes current functionality).
# Changes in:
- [x] GCP
- [ ] Azure
- [ ] AWS
- [ ] IBM
# Dev Checklist:
- [x] Added Unit Tests, wherever applicable.
- [x] Updated the Readme, if applicable.
- [x] Existing Tests pass
- [x] Verified functionality locally
- [x] Self Reviewed my code for formatting and complex business logic.M16 - Release 0.19Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/468Create index alias when index is created2023-02-13T20:29:50ZZhibin MaiCreate index alias when index is createdThis is part of solution to fix the issue [Multi kind search does not work with more than approximately 85 kinds](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/108)This is part of solution to fix the issue [Multi kind search does not work with more than approximately 85 kinds](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/108)M16 - Release 0.19Zhibin MaiZhibin Maihttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/467GC use full name for image2023-08-18T15:05:11ZAliaksandr Ramanovich (EPAM)GC use full name for imageUse full name for docker images in chartsUse full name for docker images in chartsM16 - Release 0.19Aliaksandr Ramanovich (EPAM)Aliaksandr Ramanovich (EPAM)https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/466Added config property for retry logic in rabbitmq (GONRG-6407)2023-02-01T07:33:40ZYurii Ruban [EPAM / GCP]Added config property for retry logic in rabbitmq (GONRG-6407)# Description:
Implemented retry logic for rabbitMQ.
# How to test:
1. Add property to service with rabbitMQ. (For example, Indexer) rabbitmq-retry-delay={time in ms} rabbitmq-retry-limit={retry count}
2. Check aditional exchange for q...# Description:
Implemented retry logic for rabbitMQ.
# How to test:
1. Add property to service with rabbitMQ. (For example, Indexer) rabbitmq-retry-delay={time in ms} rabbitmq-retry-limit={retry count}
2. Check aditional exchange for queue with type x-delayed-message
3. Push event with exception in structure
4. Check retry count in service logs
# Changes include:
- [x] New feature (a non-breaking change that adds functionality).
# Changes in:
- [x] GCPM16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/464[GONRG-6342] Deploy redis by indexer helm2023-08-18T15:05:13ZOleksandr Kosse (EPAM)[GONRG-6342] Deploy redis by indexer helmM16 - Release 0.19https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/463Modify files for merging all helms indexer service2023-08-18T15:05:16ZVladyslav HundarchukModify files for merging all helms indexer serviceModify files for merging all helms for indexer service.Modify files for merging all helms for indexer service.M16 - Release 0.19Vladyslav HundarchukVladyslav Hundarchukhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/460Removed audience property (GONRG-6243)2023-01-12T23:52:48ZYurii Ruban [EPAM / GCP]Removed audience property (GONRG-6243)# Description:
Removed audience property
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
# Changes in:
- [x] GCP# Description:
Removed audience property
# Changes include:
- [ ] Refactor (a non-breaking change that improves code maintainability).
# Changes in:
- [x] GCPM16 - Release 0.19Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/458fixing dependency check2023-01-09T16:50:17ZMarc Burnie [AWS]fixing dependency checkM16 - Release 0.19Marc Burnie [AWS]Marc Burnie [AWS]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/457temporarily bypass maven dependency check2023-01-09T13:12:39ZMorris Estepatemporarily bypass maven dependency checkM16 - Release 0.19Morris EstepaMorris Estepahttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/456index normalizedKind attribute under tags for all records2023-01-19T14:52:29ZMingyang Zhuindex normalizedKind attribute under tags for all recordsissue: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/78
Index normalized kind (authority + source + entity type + major version. e.g., authority:source:type:1.0.0 will be indexed as authority:source:type:...issue: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/78
Index normalized kind (authority + source + entity type + major version. e.g., authority:source:type:1.0.0 will be indexed as authority:source:type:1) under tags for all recordsM16 - Release 0.19Mingyang ZhuMingyang Zhu