[
https://issues.apache.org/jira/browse/HBASE-17320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang updated HBASE-17320:
------------------------------
Release Note:
Now you can specific the inclusive of startRow and stopRow for a scan using the
new methods withStartRow(byte[] startRow, boolean inclusive) and
withStopRow(byte[] stopRow, boolean inclusive). The old setStartRow and
setStopRow methods, and the constructors are marked as deprecated because of an
strange behavior that we will include the stopRow implicitly if startRow equals
to stopRow. This is used to support get scan in the old time. Use withStartRow
and withStopRow instead.
For developers, the ConnectionUtils.createClosestRowBefore is also marked as
deprecated as the row returned by this method is only very very close to the
current row, not closest. Avoid using this method in the future.
> Add inclusive/exclusive support for startRow and endRow of scan
> ---------------------------------------------------------------
>
> Key: HBASE-17320
> URL: https://issues.apache.org/jira/browse/HBASE-17320
> Project: HBase
> Issue Type: Sub-task
> Components: Client, scan
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-17320-v1.patch, HBASE-17320-v2.patch,
> HBASE-17320-v3.patch, HBASE-17320-v4.patch, HBASE-17320-v5.patch,
> HBASE-17320-v6.patch, HBASE-17320.patch
>
>
> This is especially useful when doing reverse scan. HBASE-17168 maybe a more
> powerful solution but we need to be careful about the atomicity, and I do not
> think we will provide the feature to end user. But I think it is OK to
> provide inclusive/exclusive option to end user.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
