Search backend (Elasticsearch) Upgrade. Part 1 - Latest v7.17.x Upgrade.

Description:

ADR: #111

• As part of the Elasticsearch migration effort, the first part was done in MR, migration from Java high level rest API to Java API client SDK.
• Elasticsearch is still with version 7.
• The main goal is to get the service functioning properly with the new Java client.

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).
• 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:

• Common code
• Azure
• AWS
• IBM
• GC
• Community Implementation

Dev Checklist:

• Added Unit Tests, wherever applicable.
• Updated the Readme, if applicable.
• Existing Tests pass
• Verified functionality locally
• Self Reviewed my code for formatting and complex business logic.

Other comments:

Any comments to approvers here

changed milestone to %M24 - Release 0.27

assigned to @Rustam_Lotsmanenko

added 1 commit

• 16d1b837 - fix get mapping

Compare with previous version

marked this merge request as ready

changed title from Draft: migration to elasticsearch java client to Search backend (Elasticsearch) Upgrade. Part 1 - Latest v7.17.x Upgrade.

added Common Code label

changed the description

added 1 commit

• 030577b3 - fix response truncation, trying to fix NPE

Compare with previous version

approved this merge request

@Rustam_Lotsmanenko Any plan to migrate the ElasticSearch client in the search service?

approved this merge request

approved this merge request

added MREnhancement label

requested review from @nthakur

added 1 commit

• d33d43f2 - cleanups and notice

Compare with previous version

reset approvals from @mzhu9, @chad, and @zmai by pushing to the branch

resolved all threads