-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-27950 ClientSideRegionScanner does not adhere to RegionScanner.nextRaw contract #5304
Conversation
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
💔 -1 overall
This message was automatically generated. |
🎊 +1 overall
This message was automatically generated. |
I updated this PR and the resulting merged commit message to link it to a new jira HBASE-27950. I realized that the old jira actually was not a problem, since the TableSnapshotInputFormat had been fixed to force ReadType.STREAM back in HBASE-26273, before HBASE-26630 was submitted. It was worth a new jira here so that we could still update ClientSideRegionScanner to honor the contract of RegionScanner.nextRaw for future proofing. |
…nextRaw contract (#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org>
…nextRaw contract (#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org>
…nextRaw contract (#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org>
I do not think force a stream read can fix the problem described in HBASE-26630? The problem is that we should use the return value of nextRaw to determine whether there are still more values. This can not be fixed by changing the ReadType. And in HBASE-26273, we still allow users to change the ReadType back to PREAD, so it should not be considered as a 'fix' even if it can fix the problem right? Opening a new issue is OK, but let's resolve HBASE-26630 as duplicated by HBASE-27950. Thanks. |
Yea, good point. Thanks, I'll fix the resolution. |
…nextRaw contract (apache#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org>
…nextRaw contract (#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org>
… to RegionScanner.nextRaw contract (apache#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org>
…nextRaw contract (apache#5304) Signed-off-by: Duo Zhang <zhangduo@apache.org> Signed-off-by: Bryan Beaudreault <bbeaudreault@apache.org> (cherry picked from commit d839fd4) Change-Id: I3d81cb0a667f4b572cbd4bac9265b4713e739f07
Jira