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-16556) The read/write timeout are not used in HTable.delete(List), HTable.get(List), and HTable.existsAll(List)
Date Thu, 09 Nov 2017 01:33:00 GMT

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

Andrew Purtell updated HBASE-16556:
-----------------------------------
    Fix Version/s: 1.4.0

> The read/write timeout are not used in HTable.delete(List), HTable.get(List), and HTable.existsAll(List)
> --------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-16556
>                 URL: https://issues.apache.org/jira/browse/HBASE-16556
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Chia-Ping Tsai
>            Assignee: Chia-Ping Tsai
>            Priority: Minor
>             Fix For: 2.0.0, 1.4.0
>
>         Attachments: HBASE-16556.branch-1.v0.patch, HBASE-16556.v0.patch
>
>
> [HBASE-15866|https://issues.apache.org/jira/browse/HBASE-15866] splits rpc timeout into
read timeout and write timeout.
> The HTable.delete(List), HTable.get(List), and HTable.existsAll(List) call AP#batch()
to submit data, but they don’t use the read/write timeout argument. So the AP will use the
rpc timeout got from hbase.rpc.timeout.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message