Indexer merge requestshttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests2021-03-04T07:49:08Zhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/106Draft: User/manishk/version from parent pom2021-03-04T07:49:08ZMANISH KUMARDraft: User/manishk/version from parent pomRemoving separate versioning in Azure pom for common core libRemoving separate versioning in Azure pom for common core libMANISH KUMARMANISH KUMARhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/122supress property mismatch warning logs, add probe delay2021-11-19T12:05:38ZAlok Joshisupress property mismatch warning logs, add probe delayLogging changes to prevent logging flood in case of mass ingestion with schema-record mismatch
Also made container probe less frequentLogging changes to prevent logging flood in case of mass ingestion with schema-record mismatch
Also made container probe less frequentAlok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/33Updaing readme doc with Istio Auth filter2021-11-19T12:05:55ZKiran VeerapaneniUpdaing readme doc with Istio Auth filterhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/226Upgrade OSDU dependencies2022-01-25T17:37:00ZDavid Diederichd.diederich@opengroup.orgUpgrade OSDU dependenciesThis includes !165 in the commit graph, so that MR will close when this one does.
Also, that will close #25.
This upgrade does more than just upgrade the core-common, but it also does that.This includes !165 in the commit graph, so that MR will close when this one does.
Also, that will close #25.
This upgrade does more than just upgrade the core-common, but it also does that.David Diederichd.diederich@opengroup.orgDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/344Fixed jackson conflict version issue2022-07-12T08:07:52ZDmitrii Novikov (EPAM)Fixed jackson conflict version issueDmitrii Novikov (EPAM)Dmitrii Novikov (EPAM)https://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/211Autoscaling and resource limits based on feature flag2022-07-12T15:41:08ZAlok JoshiAutoscaling and resource limits based on feature flagAdd autoscaling configuration with hpa and pod resource limits based on environment feature flagAdd autoscaling configuration with hpa and pod resource limits based on environment feature flagM9 - Release 0.12Alok JoshiAlok Joshihttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/294Enabling jacoco plugin in indexer2023-02-04T05:35:42ZAkanksha PrasadEnabling jacoco plugin in indexer## 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\] No
## Does this introduce a change in the ...## 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\] No
## Does this introduce a change in the cloud provider implementation, if so which cloud?
* [ ] AWS
* \[\*\] Azure
* [ ] GCP
* [ ] IBM
## Does this introduce a breaking change?
* \[YES/NO\] No
## What is the current behavior?
To give code coverage
## What is the new/expected behavior?
Showing code coverage
## Have you added/updated Unit Tests and Integration Tests?
## Any other useful informationAkanksha PrasadAkanksha Prasadhttps://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/431upgrading indexer service for the corelib changes2023-08-25T22:29:50ZNishant Vidyasagarupgrading indexer service for the corelib changesNishant VidyasagarNishant Vidyasagarhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/639Draft: test disabling properties2023-10-18T21:05:27ZNathan StrelserDraft: test disabling propertiesNathan StrelserNathan Strelserhttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/643Cherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.242023-10-19T10:29:34ZChad LeongCherry-pick 'Full Upgrade of First Party Library Dependencies' into release/0.24**Original MR**: !627
### 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**: !627
### 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-627)M21 - Release 0.24David Diederichd.diederich@opengroup.orgChad LeongSrinivasan NarayananDavid Diederichd.diederich@opengroup.orghttps://community.opengroup.org/osdu/platform/system/indexer-service/-/merge_requests/712Disable listner.schema.event.create by default2024-02-22T15:32:06ZAlok JoshiDisable listner.schema.event.create by defaultCreating an index with a new schema (no records yet) creates unnecessary data in elastic. We don't need to create such empty indexCreating an index with a new schema (no records yet) creates unnecessary data in elastic. We don't need to create such empty indexM23 - Release 0.26Alok JoshiChad LeongAlok Joshi