You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Duo Zhang (JIRA)" <ji...@apache.org> on 2018/12/19 14:47:00 UTC
[jira] [Commented] (HBASE-21618) Scan with the same
startRow(inclusive=true) and stopRow(inclusive=false) returns one result
[ https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16725061#comment-16725061 ]
Duo Zhang commented on HBASE-21618:
-----------------------------------
IIRC this is intentional to keep compatible with old code, where we consider the scan which has the same startKey and endKey as a get...
On a vacation so do not have cycles to read the code...
> Scan with the same startRow(inclusive=true) and stopRow(inclusive=false) returns one result
> -------------------------------------------------------------------------------------------
>
> Key: HBASE-21618
> URL: https://issues.apache.org/jira/browse/HBASE-21618
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 2.0.2
> Environment: hbase server 2.0.2
> hbase client 2.0.0
> Reporter: Jermy Li
> Priority: Major
>
> I expect the following code to return none result, but still return a row:
> {code:java}
> byte[] rowkey = "some key existed";
> Scan scan = new Scan();
> scan.withStartRow(rowkey, true);
> scan.withStopRow(rowkey, false);
> htable.getScanner(scan);
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)