hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Misty Stanley-Jones (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9763) Scan javadoc doesn't fully capture semantics of start and stop row
Date Wed, 10 Dec 2014 05:10:12 GMT

    [ https://issues.apache.org/jira/browse/HBASE-9763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240666#comment-14240666
] 

Misty Stanley-Jones commented on HBASE-9763:
--------------------------------------------

[~saint.ack@gmail.com] [~busbey] can one of you look this one over? It has been sitting for
a while.

> Scan javadoc doesn't fully capture semantics of start and stop row
> ------------------------------------------------------------------
>
>                 Key: HBASE-9763
>                 URL: https://issues.apache.org/jira/browse/HBASE-9763
>             Project: HBase
>          Issue Type: Bug
>          Components: documentation
>            Reporter: Gabriel Reid
>            Assignee: Gabriel Reid
>            Priority: Minor
>         Attachments: HBASE-9763.patch
>
>
> The current javadoc for Scan#setStartRow and Scan#setStopRow methods don't accurately
capture the semantics of the use of row prefix values. Both methods describe the use of a
trailing null byte to change the inclusive/exclusive the respective semantics of setStartRow
and setStopRow.
> The use of a trailing null byte for start row exclusion only works in the case that exact
full matching is done on row keys. The use of a trailing null byte for stop row inclusion
has even more limitations (see HBASE-9035).
> The basic example is having the following rows:
> {code}
> AAB
> ABB
> BBC
> BCC
> {code}
> Setting the start row to A and the stop row to B will include AAB and AB. 
> Setting the start row to A\x0 and the stop row to B\x0 will result in the same two rows
coming out of the scan, instead of having an effect on the inclusion/exclusion semantics.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message