mocktikv: avoid sorting multiple times with unstable order (#15898)#16201
Merged
zz-jason merged 3 commits intopingcap:release-4.0from Apr 9, 2020
Merged
mocktikv: avoid sorting multiple times with unstable order (#15898)#16201zz-jason merged 3 commits intopingcap:release-4.0from
zz-jason merged 3 commits intopingcap:release-4.0from
Conversation
Contributor
Author
|
/run-all-tests |
Contributor
|
/run-all-tests |
1 similar comment
Contributor
|
/run-all-tests |
Contributor
|
/rebuild |
2 similar comments
Contributor
|
/rebuild |
Contributor
|
/rebuild |
Contributor
Author
|
Your auto merge job has been accepted, waiting for 16184 |
Member
|
/run-all-tests |
Contributor
Author
|
/run-all-tests |
Contributor
Author
|
@sre-bot merge failed. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
cherry-pick #15898 to release-4.0
What problem does this PR solve?
Issue Number: close #15767
Problem Summary:
The all tuples in TopN doesn't to be sorted multiple times but resulting into unstable order, so Next() does not fetch all tuples in the same order.
What is changed and how it works?
after all tuples from its child are fetched, sort them immedrately. Then fetch data from the ordered data.
Proposal: xxx
What's Changed:
How it Works:
Related changes
Check List
Tests
Release note