Skip to content
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

kv: use last range if streaming response does not contain a range entry #13062

Merged
merged 2 commits into from
Nov 4, 2019

Conversation

SunRunAway
Copy link
Contributor

@SunRunAway SunRunAway commented Oct 31, 2019

What problem does this PR solve?

Fix #12131, see #12131 (comment)

What is changed and how it works?

use last range if streaming response does contain a range entry

Check List

Tests

  • None

Code changes

  • None

Side effects

  • None

Related changes

  • None

Release note

  • None

@codecov
Copy link

codecov bot commented Oct 31, 2019

Codecov Report

Merging #13062 into master will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             master     #13062   +/-   ##
===========================================
  Coverage   80.0462%   80.0462%           
===========================================
  Files           468        468           
  Lines        110270     110270           
===========================================
  Hits          88267      88267           
  Misses        15215      15215           
  Partials       6788       6788

@SunRunAway SunRunAway changed the title Issues/12131/streaming 2 kv: use last range if streaming response does contain a range entry Oct 31, 2019
@SunRunAway SunRunAway changed the title kv: use last range if streaming response does contain a range entry kv: use last range if streaming response does not contain a range entry Oct 31, 2019
@breezewish
Copy link
Member

BTW note that last range is a range that has already been scanned.

@SunRunAway
Copy link
Contributor Author

BTW note that last range is a range that has already been scanned.

Exactly.

@SunRunAway SunRunAway added status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. labels Nov 4, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

@SunRunAway merge failed.

@SunRunAway
Copy link
Contributor Author

/merge

@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

Your auto merge job has been accepted, waiting for 13092

@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

@SunRunAway merge failed.

@SunRunAway
Copy link
Contributor Author

/merge

@sre-bot
Copy link
Contributor

sre-bot commented Nov 4, 2019

/run-all-tests

@sre-bot sre-bot merged commit 0201f4f into pingcap:master Nov 4, 2019
@SunRunAway SunRunAway deleted the issues/12131/streaming-2 branch November 4, 2019 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/tikv status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

May receive multiple rows in streaming mode
4 participants