Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add filtered index and promotion steps to data refresh #4833
Add filtered index and promotion steps to data refresh #4833
Changes from all commits
9c72c44
390210d
262f6b9
25178f7
65b68c7
1f6b69d
9e2f4e1
aad2ea2
f91823c
6b50025
a4c9126
8b69b27
cb3e22a
94557a7
00be547
1fc7004
d06865c
89f825a
74015e1
8f429ab
bd57214
601c876
eaca371
769f248
f9def82
0cab8ca
a10bede
99d77ea
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noting that there is a separate issue for this, (and moreover the filtered index is going away).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change ensures that the data refresh always creates a new index based off the hard-coded index configuration in
es_mapping.py
, rather than by copying the configuration of the existing index.This is how the ingestion server does it currently, and was just a miss in the previous PR. It's necessary to ensure that temporary or experimental changes to the indices (for example, created using our
create_new_es_index
DAGs or similar) are not carried forward in the data refresh without making the changes permanent via a code change/PR.