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
refactor(meta): clarify the completeness of internal table catalogs #18944
refactor(meta): clarify the completeness of internal table catalogs #18944
Changes from 4 commits
b365566
2e753f3
54b30c5
1ab43fd
5adb7fe
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.
As the notification now goes after successfully scheduling and building of the job, a failure here does not always mean that the notification was sent. That's why we changed all
DROP
handlers in the frontend to beDROP .. IF EXISTS
.An alternative could be introducing a new operation like
Cleanup
for this purposes, ensuringDelete
remains strictly applied. But it seems too ad-hoc to me as there's no much other usage of it.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.
Can there be a race condition? Whereby we have
Delete
of some catalog followed byAdd
of that catalog?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.
I think not because
try_abort_creating_streaming_job
is called only aftercreate_streaming_job_inner
has returned with error, whereAdd
is either pushed into the notification queue or not issued at all. After entering thistry_abort
function, no furtherAdd
operations will occur.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.
🤔 We ensured that
CREATE
andDROP
will be properly paired in #18476 .Even if theCREATE
notification fails to send due to either a FE or meta node reboot or a broken connection between them, the creation of the mview and its internal table catalogs will still be synchronized through an initial snapshot.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.
The
internal_tables
field inCreateStreamingJobContext
will now be complete.