You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2019/10/07 18:26:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Andrew Kyle Purtell updated HBASE-21618:
----------------------------------------
    Fix Version/s:     (was: 1.5.0)

> 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, 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
(v8.3.4#803005)