[ https://issues.apache.org/jira/browse/HBASE-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated HBASE-18113: -------------------------- Comment: was deleted (was: A comment with security level 'jira-users' was removed.) > Handle old client without include_stop_row flag when startRow equals endRow > --------------------------------------------------------------------------- > > Key: HBASE-18113 > URL: https://issues.apache.org/jira/browse/HBASE-18113 > Project: HBase > Issue Type: Bug > Affects Versions: 1.4.0, 2.0.0 > Reporter: Phil Yang > Assignee: Phil Yang > Priority: Major > Fix For: 1.4.0, 2.0.0 > > Attachments: HBASE-18113.v02.patch, HBASE-18113.v02.patch, > HBASE-18113.v03.patch > > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005)