Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 15 Oct 2013 08:05:44 +0000 (UTC)
From: "Gabriel Reid (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12673839.1381824323211.64972.1381824344904@arcas>
In-Reply-To: <JIRA.12673839.1381824323211@arcas>
References: <JIRA.12673839.1381824323211@arcas>
Subject: [jira] [Created] (HBASE-9763) Scan javadoc doesn't fully capture
 semantics of start and stop row
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Gabriel Reid created HBASE-9763:
-----------------------------------

             Summary: 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
            Priority: Minor


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.1#6144)