[HBASE-18113] Handle old client without include_stop_row flag when startRow equals endRow

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.4.0, 2.0.0
• Fix Version/s: 1.4.0, 2.0.0
• Hadoop Flags: Reviewed
• Assignee: Phil Yang
• Reporter: Phil Yang
• Created: 25/May/17 10:28
• Updated: 01/Aug/18 06:23
• Resolved: 26/May/17 05:52

Description

Now we have include_start_row/include_stop_row flag in new version. Before it, startRow is include and stopRow is exclude, but when startRow=endRow there is a special logic that we consider it as a get and we should return the value of this row to client.
In the new client, if user set start=end we will change include_stop_row to true for behavior compatibility.

We should also do a special logic if old client access new server for compatibility at server.

Issue Links

• is broken by: HBASE-17320 Add inclusive/exclusive support for startRow and endRow of scan
• is broken by: HBASE-17508 Unify the implementation of small scan and regular scan for sync client