hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-18000) Make sure we always return the scanner id with ScanResponse
Date Fri, 05 May 2017 22:36:04 GMT

    [ https://issues.apache.org/jira/browse/HBASE-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15999064#comment-15999064
] 

Hudson commented on HBASE-18000:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-JDK7 #158 (See [https://builds.apache.org/job/HBase-1.3-JDK7/158/])
HBASE-18000 Make sure we always return the scanner id with ScanResponse (apurtell: rev 6545b45b1ed6231365b678bff490f8972f76a456)
* (add) hbase-server/src/test/java/org/apache/hadoop/hbase/client/TestAlwaysSetScannerId.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java


> Make sure we always return the scanner id with ScanResponse
> -----------------------------------------------------------
>
>                 Key: HBASE-18000
>                 URL: https://issues.apache.org/jira/browse/HBASE-18000
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 2.0.0, 1.4.0, 1.3.1
>            Reporter: Lars Hofhansl
>            Assignee: Duo Zhang
>             Fix For: 2.0.0, 1.4.0, 1.3.2
>
>         Attachments: HBASE-18000.patch
>
>
> Some external tooling (like OpenTSDB) relies on the scanner id to tie asynchronous responses
back to their requests.
> (see comments on HBASE-17489)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message