Indexer merge requestshttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests2023-05-04T19:44:35Zhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/533[GONRG-7061] Hide internal Indexer endpoints2023-05-04T19:44:35ZOleksandr Kosse (EPAM)[GONRG-7061] Hide internal Indexer endpointsM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/532Upgrade maven dependencies2023-05-09T06:17:40Zsaketh somarajuUpgrade maven dependenciesUpgrade maven dependency versions
[security-and-compliance issue 133](https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/133)
- [indexer-service vulnerability 22053](https://community.opengroup.org/osdu...Upgrade maven dependency versions
[security-and-compliance issue 133](https://community.opengroup.org/osdu/platform/security-and-compliance/home/-/issues/133)
- [indexer-service vulnerability 22053](https://community.opengroup.org/osdu/platform/system/indexer-service/-/security/vulnerabilities/22053)
- [indexer-service vulnerability 26379](https://community.opengroup.org/osdu/platform/system/indexer-service/-/security/vulnerabilities/26379)M18 - Release 0.21saketh somarajusaketh somarajuhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/530Added a check for RabbitMQ Retry (GONRG-6705)2023-04-27T14:35:59ZRiabokon Stanislav(EPAM)[GCP]Added a check for RabbitMQ Retry (GONRG-6705)## Type of change
- [X] Bug Fix
- [ ] Feature
## 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] GCP
- [ ] IB...## Type of change
- [X] Bug Fix
- [ ] Feature
## 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] GCP
- [ ] IBM
## Does this introduce a breaking change?
- [NO]
## What is the new/expected behavior?
Updated oqm mappers.M18 - Release 0.21Riabokon Stanislav(EPAM)[GCP]Riabokon Stanislav(EPAM)[GCP]https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/529Revert "Merge branch 'GONGR-6885-reduce_requests_according_to_VPA'2023-08-18T15:04:59ZOleksandr Kosse (EPAM)Revert "Merge branch 'GONGR-6885-reduce_requests_according_to_VPA'This reverts merge request !526This reverts merge request !526M18 - Release 0.21https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/528Set FailOnError to false2023-05-03T19:26:32ZYash DholakiaSet FailOnError to falseSet FailOnError to false so build does not fail when dependency-check-maven fails.Set FailOnError to false so build does not fail when dependency-check-maven fails.M18 - Release 0.21Yash DholakiaYash Dholakiahttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/527tweak params to improve reindex performance2023-04-25T14:02:09ZRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comtweak params to improve reindex performanceIssue: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/66
# Description:
Increase record ids request by kind from 20 to 1000.
Added scheduled publisher to postpone reindex events with the `force_clean=tru...Issue: https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/66
# Description:
Increase record ids request by kind from 20 to 1000.
Added scheduled publisher to postpone reindex events with the `force_clean=true` param.
# How to test:
Does functionality was tested and how?
# Changes include:
- [x] Refactor (a non-breaking change that improves code maintainability).
- [ ] 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] Google Cloud
- [ ] Azure
- [ ] AWS
- [ ] IBM
# Dev Checklist:
- [ ] Added Unit Tests, wherever applicable.
- [ ] Updated the Readme, if applicable.
- [x] Existing Tests pass
- [x] Verified functionality locally
- [x] Self Reviewed my code for formatting and complex business logic.M18 - Release 0.21Rustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comRustam Lotsmanenko (EPAM)rustam_lotsmanenko@epam.comhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/526GONGR-6885 Reduce requests according to VPA2023-08-18T15:05:01ZAndriy Halka [EPAM / GCP]GONGR-6885 Reduce requests according to VPAM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/525AWS: Fixes user token timeout when a lengthy reindexing is started2023-08-18T15:05:03ZDerek HudsonAWS: Fixes user token timeout when a lengthy reindexing is startedFixes user token timeout when a lengthy reindexing procedure is initiated by using a service principal rather than the user's more temporary tokens.
Note: this is based on a stale master branch. The pipeline stages for GCP are failing b...Fixes user token timeout when a lengthy reindexing procedure is initiated by using a service principal rather than the user's more temporary tokens.
Note: this is based on a stale master branch. The pipeline stages for GCP are failing because this is based on a stale master branch. The branch this was based on is [here](https://community.opengroup.org/osdu/platform/system/indexer-service/-/pipelines/179562), where the pipeline is also failing for those same issues.M18 - Release 0.21Yong ZengDerek HudsonYong Zenghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/524OpenAPI 3.0 Documentation using springdoc2023-04-21T12:58:59ZThulasi Dass SubramanianOpenAPI 3.0 Documentation using springdoc**Link to ADR(Architecture Decision Record)** : [Swagger using springdoc-openapi](https://community.opengroup.org/osdu/platform/system/home/-/issues/97)
## OpenAPI 3.0 related changes
* upgraded to latest **springdoc openapi** latest v...**Link to ADR(Architecture Decision Record)** : [Swagger using springdoc-openapi](https://community.opengroup.org/osdu/platform/system/home/-/issues/97)
## OpenAPI 3.0 related changes
* upgraded to latest **springdoc openapi** latest version [1.6.14](https://mvnrepository.com/artifact/org.springdoc/springdoc-openapi-ui/1.6.14)
* used **[@OpenAPIDefinition](https://docs.swagger.io/swagger-core/v2.0.9/apidocs/io/swagger/v3/oas/annotations/OpenAPIDefinition.html)** annotation to populate OpenAPI Object fields *\[info, tags, servers, security\]*
* Documented the below API's with OpenAPI 3.0 **Annotations**
- CleanupIndicies API
- PartitionSetup API
- Reindex API
- RecordIndexer API(Internal API, marked as 'Hidden' for documentation)
- Health Check API
- Info API
* Added the standard HTTP Response(4xx, 5x\*\*\*\*x) for API Responses
* Custom Path for
* **Swagger UI**: https://host/context-path/swagger (will redirect to https://host/context-path/swagger-ui/index.html)
* **api-docs (JSON)** : https://host/context-path/api-docs
* **api-docs (YAML)** : https://host/context-path/api-docs.yaml
* Azure Swagger GLAB(for Reference)
* **Swagger UI**: https://osdu-glab.msft-osdu-test.org/api/indexer/v2/swagger (will redirect to https://osdu-glab.msft-osdu-test.org/api/indexer/v2/swagger-ui/index.html)
* **api-docs (JSON)** : https://osdu-glab.msft-osdu-test.org/api/indexer/v2/api-docs
* **api-docs (YAML)** :https://osdu-glab.msft-osdu-test.org/api/indexer/v2/api-docs.yaml
## Other Changes
- **Configurable** descriptions managed in [swagger.properties](url)
- Deleted HomeController
- Marked the 'WhoamiController' as 'Hidden' for documentation
- Updated Readme for swagger related information
## References
- https://springdoc.org/faq.html#_can_i_use_spring_property_with_swagger_annotations
- https://springdoc.org/migrating-from-springfox.htmlM18 - Release 0.21Thulasi Dass SubramanianThulasi Dass Subramanianhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/518Full Upgrade of First Party Library Dependencies for Release 0.202023-05-22T15:18:25ZDavid Diederichd.diederich@opengroup.orgFull Upgrade of First Party Library Dependencies for Release 0.20This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will ...This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release.
The intent is to try to fully upgrade all dependent libraries to see if the latest code will work.
It is expected that these will often fail, since the upgrades were previously rejected for failing pipelines and have not been directly addressed yet.
This upgrade should only be merged in the CI pipeline reports success.
If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library.
But significant upgrade efforts should not occur on this MR, as part of the release tagging process.
Instead, significant work should be scheduled for a subsequent milestone.
This MR may co-exist with a separate, smaller upgrade MR.
If both pass, this one should be used instead.
### Dependency Information Before the Upgrade
```
Branch: master
SHA: 96df4fc279ee82ede9c052d2411e77ef7f9dd177
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | ---------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.12.0-rc10 |
| core-lib-gcp | 0.20.0-rc2 | |
| os-core-lib-aws | 0.21.0-rc1 | 0.19.0-rc3 |
| obm | 0.19.0 | |
| oqm | 0.19.0 | |
| os-core-common | 0.19.0, 0.19.0-rc6 | 0.14.0-rc8 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.13.0 |
| osm | 0.20.0-rc2 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.1, 2.13.2.2, 2.13.4.2 | 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.yaml.snakeyaml | 2.0 | 1.26 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade
SHA: 5d54b9fa233d653d1d2a69fc420d1472a5eee660
Maven: 0.21.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | ---------------------- |
| core-lib-azure | 0.20.0 | 0.20.0 |
| core-lib-gc | 0.20.0 | |
| os-core-lib-aws | 0.21.0-rc2 | 0.21.0-rc2 |
| obm | 0.20.0 | |
| oqm | 0.20.0 | |
| os-core-common | 0.20.1 | 0.20.1 |
| os-core-lib-ibm | 0.20.0 | 0.20.0 |
| osm | 0.20.0 | |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.1, 2.13.2.2, 2.13.4.2 | 2.13.2.2, 2.13.2 |
| (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-to-slf4j | 2.17.1 | 2.11.2, 2.13.0 |
| (3rd Party) org.yaml.snakeyaml | 2.0 | 1.26, 1.27, 2.0 |M18 - Release 0.21Okoun-Ola Fabien HouetoBrindaban DasYauhen Shaliou [EPAM/GCP]Srinivasan NarayananOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/517Updating core lib aws to latest rc version2023-04-07T17:37:36ZManish JangidUpdating core lib aws to latest rc versionUpdating core lib aws to latest rc versionUpdating core lib aws to latest rc versionM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/516ReadOnlyRootFileSystem changes for AWS2023-04-07T18:40:24ZAbhay JoshiReadOnlyRootFileSystem changes for AWScommit 6584a46b
Author: Abhay <bios@amazon.com>
Date: Tue Mar 21 2023 08:40:01 GMT-0700 (Pacific Daylight Time)
removing old ssl stuff
commit d6d80ec7
Author: Abhay <bios@amazon.com>
Date: Tue Mar 21 2023 07:29:05 GMT-0700 (Pacific...commit 6584a46b
Author: Abhay <bios@amazon.com>
Date: Tue Mar 21 2023 08:40:01 GMT-0700 (Pacific Daylight Time)
removing old ssl stuff
commit d6d80ec7
Author: Abhay <bios@amazon.com>
Date: Tue Mar 21 2023 07:29:05 GMT-0700 (Pacific Daylight Time)
Renaming variable
commit a2ef5304
Author: Abhay <bios@amazon.com>
Date: Mon Mar 20 2023 10:44:26 GMT-0700 (Pacific Daylight Time)
adding changes for rootFilesystem
(cherry picked from commit 31267f749fc7b067c4af231273f3e3250056013c)M18 - Release 0.21Okoun-Ola Fabien HouetoAbhay JoshiOkoun-Ola Fabien Houetohttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/514remove legacy code that's not being used by any API2023-04-24T14:30:50ZNeelesh Thakurremove legacy code that's not being used by any APIM18 - Release 0.21https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/496Provide an endpoint to create aliases for all existing indices that do not ha...2023-05-11T12:33:50ZZhibin MaiProvide an endpoint to create aliases for all existing indices that do not have aliasesThis is follow-up of fix for issue [Multi kind search does not work with more than approximately 85 kinds](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/108).
In this MR, we add an endpoint that allows clo...This is follow-up of fix for issue [Multi kind search does not work with more than approximately 85 kinds](https://community.opengroup.org/osdu/platform/system/search-service/-/issues/108).
In this MR, we add an endpoint that allows cloud operators to create aliases for all existing indices. Doing that, queries from a given data partition won't trigger the alias creation operation in the search service after the endpoint is called once for the given data partition.
Please note that previous change in search service still works even the cloud operators don't call this new endpoint if they don't have time now. However, it is still recommended to explicitly call it once for all existing data partitions.M18 - Release 0.21Zhibin MaiZhibin Maihttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/465Index extended properties defined in property configurations2023-07-13T17:44:36ZZhibin MaiIndex extended properties defined in property configurationsThis is one of the MRs for [ADR: Configurable Index Extensions and De-Normalizations](https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/81)
It depends MR [Make sure that the indexer-queue for azure forwards t...This is one of the MRs for [ADR: Configurable Index Extensions and De-Normalizations](https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/81)
It depends MR [Make sure that the indexer-queue for azure forwards the ancestry_kinds...](https://community.opengroup.org/osdu/platform/system/indexer-queue/-/merge_requests/310) to support the solution that prevents infinite loop of re-index.
We introduced chasing mechanisms to solve the issue of the index order and provided a solution to prevent infinite loop of re-index.
<details>
<summary markdown="span">How index chasing work</summary>
1. How to update the indexed documents of children records when a parent record is updated:
As we know, a parent kind can have many children kinds. For example, a Wellbore kind can have children kinds: WellLog, WellboreTrajectory, WellboreMarkerSet and etc. In most cases, not all children kinds need to extend the parent kind. And There is no standard/unique way for all children kinds that define the reference (e.g. data.WellboreId in WellLog record) to the parent record.
So we need to have an efficient way to find all the children that need to extend the parent record's properties.
- When a child record is indexed and it needs to extend one or more properties from its parent records, a new property "data.AssociatedIdentities" as string array is created in the children's documents. The parent ids are inserted into this property.
- When a parent record is indexed, at the end, it will use its id to search children records. Then one or multiple messages are constructed and sent out to simulate the record change events for all the children records that need to be re-indexed. Similar query will like this:
```
{
kind: "*:*:*:*",
query: "data.AssociatedIdentities:\"<parent record id>\""
}
```
2. How to update the indexed documents of parent records when a child record is updated:
As child record has all the references (ids) to its parent records, in order to find out which parent record(s) should be re-indexed, the query as below can be used to find out whether there is any IndexPropertyConfiguration that refers to the child kind
```
{
kind: "osdu:wks:reference-data--IndexPropertyPathConfiguration:*",
query: "nested(data.Configurations, nested(data.Configurations.Paths, (RelatedObjectsSpec.RelationshipDirection: ParentToChildren AND RelatedObjectsSpec.RelatedObjectKind:\"<child kind>\")))"
}
```
The above search result will be cached. If there is any IndexPropertyConfiguration that defines "ParentToChildren" relationship, it will find out which parent reocrd(s) should be re-indexed. Then one or multiple messages are constructed and sent out to simulate the record change events for all the parent records that need to be re-indexed .
</details>
<details>
<summary markdown="span">How to prevent infinite loop of re-index/index chasing</summary>
As we mentioned, one or more messages will be sent out to simulate the record change events in order to re-index the parent or children records. In the [ADR](https://community.opengroup.org/osdu/platform/system/indexer-service/-/issues/81), the Use Case 3 and Use Case 4 demonstrate the possibility that a circular reference can be defined in the IndexPropertyPathConfiguration.
Here is the normal record change event message when multiple WellLog records are updated:
```
{
"data": "[{\"id\":\"opendes:work-product-component--WellLog:23b7dfde2c1349d58a0f97ae78bff9df\",\"kind\":\"osdu:wks:work-product-component--WellLog:1.2.0\",\"op\":\"update\"}, {\"id\":\"opendes:work-product-component--WellLog:9b579416f23c4f36af4a00c10657babe\",\"kind\":\"osdu:wks:work-product-component--WellLog:1.2.0\",\"op\":\"update\"}]",
"attributes": {
"data-partition-id": "{{data-partition-id}}"
}
}
```
In order to prevent infinite loop of re-index, an extra information is piggyback when a event change message is sent out for the given records. The source kind that triggers the re-index of other records will be part of the message. In Case 3 example, the record change event message will be constructed as below:
```
{
"data": "[{\"id\":\"opendes:work-product-component--WellLog:23b7dfde2c1349d58a0f97ae78bff9df\",\"kind\":\"osdu:wks:work-product-component--WellLog:1.2.0\",\"op\":\"update\"}, {\"id\":\"opendes:work-product-component--WellLog:9b579416f23c4f36af4a00c10657babe\",\"kind\":\"osdu:wks:work-product-component--WellLog:1.2.0\",\"op\":\"update\"}]",
"attributes": {
"data-partition-id": "{{data-partition-id}}",
"ancestry_kinds": "osdu:wks:master-data--Wellbore:1.1.1"
}
}
```
When the above message is received and the WellLog children records are re-indexed, the information in the "ancestry_kinds" can be used to prevent trigger the re-index of the parent Wellbore record.
The ancestry_kinds can include multiple kinds that are separated by comma. For example, Well record triggers the index of Wellbore record and Wellbore record triggers the index of WellLog records, the message can be:
```
{
"data": "[{\"id\":\"opendes:work-product-component--WellLog:23b7dfde2c1349d58a0f97ae78bff9df\",\"kind\":\"osdu:wks:work-product-component--WellLog:1.2.0\",\"op\":\"update\"}, {\"id\":\"opendes:work-product-component--WellLog:9b579416f23c4f36af4a00c10657babe\",\"kind\":\"osdu:wks:work-product-component--WellLog:1.2.0\",\"op\":\"update\"}]",
"attributes": {
"data-partition-id": "{{data-partition-id}}",
"ancestry_kinds": "osdu:wks:master-data--Well:1.1.0,osdu:wks:master-data--Wellbore:1.1.1"
}
}
```
</details>M18 - Release 0.21Zhibin MaiZhibin Maihttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/438ADR66/81 prototype2023-04-28T11:18:44ZZhibin MaiADR66/81 prototypeADR [66](https://gitlab.opengroup.org/osdu/subcommittees/ea/work-products/adr-elaboration/-/issues/66) (original elaboration and trade-off)
ADR #81 for this repo.ADR [66](https://gitlab.opengroup.org/osdu/subcommittees/ea/work-products/adr-elaboration/-/issues/66) (original elaboration and trade-off)
ADR #81 for this repo.M18 - Release 0.21Zhibin MaiZhibin Maihttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/586Upgrade First Party Library Dependencies for Release 0.222023-07-18T07:06:57ZDavid Diederichd.diederich@opengroup.orgUpgrade 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: a2b71603f34b4c4f5b319837537abffcd83dda83
Maven: 0.23.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | ---------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.12.0-rc10 |
| core-lib-gc | 0.21.0 | |
| os-core-lib-aws | 0.21.0 | 0.21.0 |
| oqm | 0.21.0 | |
| os-core-common | 0.21.0 | 0.14.0-rc8 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.13.0 |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.1, 2.13.2.2, 2.13.4.2 | 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.yaml.snakeyaml | 2.0 | 1.26 |
### Dependency Information After the Upgrade
```
Branch: dependency-upgrade-2
SHA: 535e9f9b3cd9d2a672d8d681de0d299363d5169d
Maven: 0.23.0-SNAPSHOT
```
| Maven Dependencies | _Root_ | testing/ |
| ------------------------------------------------------- | -------------------------- | ---------------------- |
| core-lib-azure | 0.20.0-rc5 | 0.12.0-rc10 |
| core-lib-gc | 0.22.1 | |
| os-core-lib-aws | 0.22.0 | 0.22.0 |
| oqm | 0.22.0 | |
| os-core-common | 0.22.0 | 0.14.0-rc8 |
| os-core-lib-ibm | 0.16.0-rc1 | 0.13.0 |
| (3rd Party) com.fasterxml.jackson.core.jackson-databind | 2.14.1, 2.13.2.2, 2.13.4.2 | 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.yaml.snakeyaml | 2.0 | 1.26 |M19 - Release 0.22https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/585Cherry-pick 'Prevent any exception from Augmenter functions to corrupt the no...2023-07-17T13:32:34ZChad LeongCherry-pick 'Prevent any exception from Augmenter functions to corrupt the normal indexing' into release/0.22**Original MR**: !583
### 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**: !583
### 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-583)M19 - Release 0.22David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/584Merge branch 'GONRG-7438_Add_istio_sidecars_in_DF_light_mode' into 'master'2023-07-14T11:53:03ZAndrei Skorkin [EPAM / GCP]Merge branch 'GONRG-7438_Add_istio_sidecars_in_DF_light_mode' into 'master'Add istio sidecar to indexer (GONRG-7438)
See merge request osdu/platform/system/indexer-service!581
(cherry picked from commit 2e0a49ac1e5875718bbae8bd4faa5bca17487927)
ed95bf48 add istio sidecar to indexerAdd istio sidecar to indexer (GONRG-7438)
See merge request osdu/platform/system/indexer-service!581
(cherry picked from commit 2e0a49ac1e5875718bbae8bd4faa5bca17487927)
ed95bf48 add istio sidecar to indexerM19 - Release 0.22Chad LeongChad Leonghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/583Prevent any exception from Augmenter functions to corrupt the normal indexing2023-07-17T13:32:00ZZhibin MaiPrevent any exception from Augmenter functions to corrupt the normal indexingThis is follow-up [Index extended properties defined in property configurations](https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/465)
In this MR is to prevent any exception from Augmenter functions ...This is follow-up [Index extended properties defined in property configurations](https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/465)
In this MR is to prevent any exception from Augmenter functions to corrupt the normal data indexing and log invalid PropertyConfigurations caused by user mistake. Both will help debug the unexpected results from Augmenter.M19 - Release 0.22Zhibin MaiZhibin Mai