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
feat(batch): support query data without checkpoint #5850
feat(batch): support query data without checkpoint #5850
Changes from 13 commits
bd12005
55737f8
0bf0741
ec56d6f
00985fa
ded4e8a
d6b94d4
a30588d
95d62f9
0765dc1
c04db97
fa1c428
ebd8c21
df45da3
08e6a57
e1a0aa2
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.
May I ask the reason to read
Checkpoint
by default? Do we have the plan to change the default value toAll
?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.
When VISIBILITY_MODE=all, a FLUSH command no more enforce a checkpoint barrier, thus may surprise user that their data is still lost even they have FLUSHed. Besides this, I don't think of other concerns not to use VISIBILITY_MODE=all by default. @hzxa21 @xxhZs
Or shall we even change FLUSH back to always enforce a checkpoint?
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.
+1 to enable VISIBILITY_MODE=all by default since it provides better freshness and normally user doesn't pay serious attention to data rewind.
This sounds reasonable to me since
FLUSH
normally indicates persistence.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.
+1, agree with Patrick
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.
fix in #7188
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.
Some earlier discussions: #4966 (comment)
Should we adopt the
CHECKPOINT
command now?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.
Refactor to embed
only_checkpoint_visible
here, instead of previously@xxhZs