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
Provide a reason for not having an execution plan (MySQL) #9569
Provide a reason for not having an execution plan (MySQL) #9569
Changes from 6 commits
a61a0d1
c355f2e
2d47885
1fd035f
5adf5f0
19ce6df
999f97d
92e3a78
47ba7d1
5e1edd5
dbab18b
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.
I wonder if we should collect all of the errors, by strategy? The problem with this approach is that we'll only get the error for the last strategy, potentially hiding other setup issues.
Perhaps for mysql instead of just one
(code, reason)
we have a map ofstrategy -> (code, reason)
? Maybe under a different key:collection_error_by_strategy
@justiniso what do you think?
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.
Discussed offline, but for context, there are cases where we wont have a strategy to make a mapping of
strategy -> (code, msg)
(i.e_can_explain()
) so we were thinking, what if we simplify it to where we structure it as[{strategy, code, message}, ...]
undercollection_errors
to be more universal?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.
Decided to implement this approach, we can revert if necessary.