[
https://issues.apache.org/jira/browse/HBASE-16575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474268#comment-15474268
]
Andrew Purtell commented on HBASE-16575:
----------------------------------------
The AP was written so it could work with read ops as well as mutations. There
are comments in the code to this effect indicating that as intent at the time
it was developed. I would be interested to see if we can follow through on a
unification of client RPC logic.
> unify the semantic of RRCI#callWithRetries and RRCI#callWithoutRetries when
> the maxAttempts is configured to one
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-16575
> URL: https://issues.apache.org/jira/browse/HBASE-16575
> Project: HBase
> Issue Type: Bug
> Reporter: ChiaPing Tsai
> Priority: Minor
>
> It seems to me that RRCI#callWithRetries and RRCI#callWithoutRetries should
> have the same logic if the maxAttempts is configured to one. But there are
> some difference are shown below:
> 1) timeout
> 2) failure handle
> The quick solution is that we always call the RRCI#callWithRetries in the
> RRCI#callWithoutRetries when the maxAttempts is configured to one.
> Any comment? Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
