Details
-
Bug
-
Status: Resolved
-
Critical
-
Resolution: Auto Closed
-
None
-
None
-
None
Description
I noticed the following issue digging through ACCUMULO-3616.
ClientContext.java
public long getClientTimeoutInMillis() { return getConfiguration().getTimeInMillis(Property.GENERAL_RPC_TIMEOUT); }
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.