Send schema_version value to the ElasticIndexer project
What does this MR do and why?
This MR will send the value of the schema_version
for blob
, commit
, and wiki
to the ElasticIndexer project. With this change, we don't have to touch the ElasticIndexer
project to update the schema_version
value.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
- Ensure the Elasticsearch is enabled.
Wiki test
- Create or update a project or group wiki. Now check on Elastic the value of the
schema_version
for this wiki. It must be2308
. - Now update the
schema_version
here to something else. For instance23_12
- Now again create or update a project or group wiki. Now check on Elastic the value of
schema_version
for this wiki. It must be2312
.
Blob and Commit test
- Create or update some code. Now check on Elastic the value of the
schema_version
for this blob. It must be2308
. - Now update the
schema_version
here to something else. For instance23_11
- Now update the
schema_version
here to something else. For instance23_10
- Now again create or update some code. Now check on Elastic the value of
schema_version
for this blob. It must be2311
. - Also check on Elastic the value of the
schema_version
for the new commit. It must be2310
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #424494 (closed)
Edited by Ravi Kumar