This repository was archived by the owner on Aug 23, 2023. It is now read-only.
[WIP] Regularly reload meta records #1480
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
this is necessary to ensure that all the statements get executed in the right order. also makes the meta tags argument of the upsert post requests not required, this is necessary to be able to delete meta records.
replay
force-pushed
the
regularly_reload_meta_records
branch
2 times, most recently
from
5cc5439 to
9d26422
Compare
|
has been implemented in #1471 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This PR is based on the branch of #1471. Reviewing it only makes sense if #1471 has already been merged.
Implements the functionality to reload the meta records from the Cassandra store at a defined interval, this is necessary for reaching consistency eventually. Additionally, it adds a method to hash all present meta records and compare the hashes between sets of meta records, this is necessary to avoid clearing the enrichment cache when none of the meta records have changed.