[
https://issues.apache.org/jira/browse/HBASE-17372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15784638#comment-15784638
]
stack commented on HBASE-17372:
-------------------------------
My comment comes from seeing how much you are able to cleanup when you
aggregate all timeouts in a single class (RetryConfig). Having a generic
operationconfig object instead of a particular retryconfig seems like a safer
bet.
If RetyConfig is in classes marked private and it seems to be all client-side
-- no protos involved -- then we can change it later if we need to add config
beyond retry/timeout. In this case, +1 on the patch.
> Make AsyncTable thread safe
> ---------------------------
>
> Key: HBASE-17372
> URL: https://issues.apache.org/jira/browse/HBASE-17372
> Project: HBase
> Issue Type: Sub-task
> Components: asyncclient, Client
> Affects Versions: 2.0.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0
>
> Attachments: HBASE-17372-v1.patch, HBASE-17372.patch
>
>
> The most methods are already thread safe. The problem is that we have some
> methods that used to set timeout, we need to remove these methods and add a
> parameter for each call to specific timeout settings.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
