-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
executor: init builder startTS in buildTableDual
#6830
Conversation
Fixes panic when table dual is index join outer table.
Is there a related issue? |
/run-all-tests |
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.
LGTM
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.
LGTM
newExecuorBuilder
buildTableDual
buildTableDual
buildTableDual
/run-all-tests |
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.
LGTM
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.
LGTM
@coocood We need to cherry-pick this to the release-2.0. |
Fixes #6828
What have you changed? (mandatory)
When we build an index join executor with outer table is table dual, we never call
b.getStartTS
during build time.But later when we execute the query, we use the builder to build inner table which needs
startTS
, but by then, the transaction is set to invalid, then we panic.This PR init the startTS in
executorBuilder.buildTableDual
to fix the panic issue.What are the type of the changes (mandatory)?
How has this PR been tested (mandatory)?