[HBASE-17320] Add inclusive/exclusive support for startRow and endRow of scan

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Component/s: Client, Scanners
• Hadoop Flags: Reviewed

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.

• Assignee: Duo Zhang
• Reporter: Duo Zhang
• Created: 15/Dec/16 12:47
• Updated: 14/Feb/20 21:52
• Resolved: 29/Dec/16 01:53

Description

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.

Issue Links

• breaks: HBASE-18113 Handle old client without include_stop_row flag when startRow equals endRow
• causes: HBASE-23842 Remove deprecated Scan(byte[], byte[]) from Scan
• causes: HBASE-23843 Remove deprecated Scan(byte[]) from Scan
• causes: HBASE-23844 Remove deprecated Scan(byte[], Filter) from Scan
• causes: HBASE-23847 Remove deprecated setStartRow(byte[]) from Scan
• causes: HBASE-23848 Remove deprecated setStopRow(byte[]) from Scan
• relates to: HBASE-17583 Add inclusive/exclusive support for startRow and endRow of scan for sync client
• links to: reviewboard