hbase-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HBASE-18000?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andrew Purtell updated HBASE-18000:
-----------------------------------
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

Pushed to master, branch-1, and branch-1.3. I ran the hbase-client tests for each branch,
including new unit TestAlwaysSetScannerId and they all passed. 

> 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