Gcp full reindex (GONRG-1534)
Description:
As a part of the migration to a new Elastic 7 we need some functionality
that will allow us to do full reindex of Records registered in Storage service.
Added new endpoint: PATCH /api/indexer/v2/reindex?force_clean=false
- Get all kind from Storage
- Clean all old indexes in Elastic
- Iterate over kinds and do reindex
How to test:
Functionality was tested locally, with local elastic(v6 & v7)
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:
-
GCP -
Azure -
AWS -
IBM
Dev Checklist:
-
Existing Tests pass -
Verified functionality locally -
Self Reviewed my code for formatting and complex business logic.
Other comments:
Functionality was implemented with reusing existing logic for reindex of a single kind, to reduce common code changes, thus due to architectural features, request cannot be executed asynchronously, and response may be detained.
Merge request reports
Activity
added AWS Azure Common Code GC IBM labels
- Resolved by Rustam Lotsmanenko (EPAM)
- Resolved by Dmitriy Rudko
@Rustam_Lotsmanenko, @rostislav.dublin - please take a look at failing IT for GCP and IBM
added 4 commits
-
10f40b57...24f5206c - 3 commits from branch
master
- 9e0358db - Merge branch 'master' into gcp-full-reindex
-
10f40b57...24f5206c - 3 commits from branch
@bhushanrade @shrikgar Please check this
@anujgupta, @bhushanrade, @shrikgar - It looks like that IBM tests are failing in master as well. Don't you mind if we will merge this change?
@osdu/platform/roles/trusted-committers GCP IBM Azure AWS, this is my second polite request to review and approve this MR which has changes in core. We merge it today evening in case of no your objections arrived. cc: @Dmitriy_Rudko @Kateryna_Kurach
mentioned in commit af0d36ee
added MRNew Feature label
changed milestone to %M3 - Release 0.5