chore: Simplification of store legacy code #2931
Merged
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
|
You can find the image built from this PR at Built from cafccff |
Ivansete-status
requested review from
NagyZoltanPeter,
gabrielmer and
darshankabariya
gabrielmer
approved these changes
Jul 30, 2024
NagyZoltanPeter
approved these changes
Jul 30, 2024
Ivansete-status
deleted the
avoid-collisions-between-legacy-and-current-archive
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
While enhancing postgres queries I noticed that there is some conflict between legacy-store and future store.
This PR is aimed to mitigate those collisions by removing unnecessary code and giving the responsibility of partition management, and retention policy, only to the new-future store archive driver.