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, 12 May 2017 04:39:04 GMT

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

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

SUCCESS: Integrated in Jenkins build HBase-Trunk_matrix #2994 (See [https://builds.apache.org/job/HBase-Trunk_matrix/2994/])
Amend HBASE-18000 Make sure we always return the scanner id with (apurtell: rev c833473619d5a2ff9437d62f2ea14ac772288304)
* (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
>          Components: regionserver
>    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-addendum-1-branch-1.3.patch, HBASE-18000-addendum-1.patch,
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