[ADH-5313] Fix problems during file rename syncing #132
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
…files, leave only FIFO strategy
tigrulya-exe
force-pushed
the
bugfix/ADH-5313-fix-append-delete-chain
branch
from
ef2dd0b to
1d5b38c
Compare
iamlapa
approved these changes
Nov 20, 2024
tigrulya-exe
changed the title
…-fill-metastore [ADH-5351] Use CreateEvent to add information about file to Metastore
…x/ADH-5313-fix-append-delete-chain
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.
InotifyEventAppliergenerates renameFileDifffor all files related to the rename event from INotify andCopySchedulermerges them to the corresponding file diff chains. In case if there are pendingAPPENDdiffs for the rename source path, scheduler cancels them and recreates with new name. Rename operation itself happens only once for the rename root path regardless of whether it is a file or a directory.smart.sync.schedule.strategyoption, controlling the order of scheduling sync files and left only FIFO strategy to avoid some corner cases where consistency is broken.deleteaction idempotent