[
https://issues.apache.org/jira/browse/HBASE-21618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16737802#comment-16737802
]
Sean Busbey commented on HBASE-21618:
-------------------------------------
yeah it changes incorrect behavior and is (rightly) marked Critical. As-is the
only thing that'll show up in our release notes is the jira subject, which only
mentions the old incorrect behavior (without labeling it as such).
> 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
> Assignee: Guanghao Zhang
> Priority: Critical
> Fix For: 3.0.0, 1.5.0, 2.2.0, 2.1.2, 2.0.4, 1.4.10
>
> Attachments: HBASE-21618.branch-1.001.patch,
> HBASE-21618.master.001.patch, HBASE-21618.master.002.patch,
> HBASE-21618.master.003.patch
>
>
> 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)
