[
https://issues.apache.org/jira/browse/HBASE-18113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026080#comment-16026080
]
Hudson commented on HBASE-18113:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3079 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/3079/])
HBASE-18113 Handle old client without include_stop_row flag when (yangzhe1991:
rev b74474dfc9ba0aef237016737adee95e55c637f6)
* (edit)
hbase-client/src/main/java/org/apache/hadoop/hbase/shaded/protobuf/ProtobufUtil.java
* (add)
hbase-client/src/main/java/org/apache/hadoop/hbase/client/ClientUtil.java
* (edit) hbase-client/src/main/java/org/apache/hadoop/hbase/client/Scan.java
> 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: 2.0.0, 1.4.0
> Reporter: Phil Yang
> Assignee: Phil Yang
> Fix For: 2.0.0, 1.4.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
(v6.3.15#6346)
