You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/04/04 04:17:33 UTC
[jira] [Updated] (ACCUMULO-3619) GENERAL_RPC_TIMEOUT not exposed
via ClientProperty's
[ https://issues.apache.org/jira/browse/ACCUMULO-3619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Elser updated ACCUMULO-3619:
---------------------------------
Fix Version/s: (was: 1.7.0)
1.8.0
> GENERAL_RPC_TIMEOUT not exposed via ClientProperty's
> ----------------------------------------------------
>
> Key: ACCUMULO-3619
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3619
> Project: Accumulo
> Issue Type: Bug
> Components: client
> Reporter: Josh Elser
> Priority: Critical
> Fix For: 1.8.0
>
>
> I noticed the following issue digging through ACCUMULO-3616.
> {code:title=ClientContext.java|borderStyle=solid}
> public long getClientTimeoutInMillis() {
> return getConfiguration().getTimeInMillis(Property.GENERAL_RPC_TIMEOUT);
> }
> {code}
> In the client API impl, we extract the RPC timeout using a server-side Property with no property in existence in the client API through ClientProperty.
> While it would be best to change this in 1.6 (as it's a bug IMO), semver would keep us from doing that. Given that it's gone a few releases without anyone noticing, it's probably not critical to buck the processes. Fix it before 1.7.0 comes out.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)