force index in iteration range end value queries #1245
Closed
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
|
Probably nitpicking but the spacing / formatting is off on the SQL queries, at least on Github. The other lines use tabs + spaces and you only used spaces. |
thank you for your advise, I'll modify it to keep consistent. |
|
@timvaillancourt would you please take the time to reivew it? |
|
@wangzihuacool I believe this is resolved by a similar PR that is on Please test and re-open if this is not the case. Thanks! |
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.
Description
This PR forces the unique-key index to be used in iteration range end value queries when copying data to the _gho table.
Force the unique-key index to avoid inappropriate optimizer selection, as discussed in #1242 .