[
https://issues.apache.org/jira/browse/ACCUMULO-2867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christopher Tubbs resolved ACCUMULO-2867.
-----------------------------------------
Resolution: Not A Problem
Closing due to this issue being quite stale, and not very specific and
actionable. The thrift helper classes have been changed and improved many times
since this issue was created, so this may be OBE. If there is something more to
be done for this, please open a new issue or PR at
https://github.com/apache/accumulo
> Consolidate Thrift connection helper classes
> --------------------------------------------
>
> Key: ACCUMULO-2867
> URL: https://issues.apache.org/jira/browse/ACCUMULO-2867
> Project: Accumulo
> Issue Type: Sub-task
> Components: client, master, replication, tserver
> Reporter: Josh Elser
> Priority: Minor
>
> Came up during the review of ACCUMULO-378:
> ReplicationClient, MasterClient, and ThriftUtil are all classes with lots of
> static methods used to make executing RPC against a remote service much
> easier with nice constructs (like getting a typed return object).
> The downside is that they have lots of implicit gotchas contained (implicit
> retries, network failure handling, etc), which make them easier to use by the
> invoking code, but very complex beasts.
> It would be good to consolidate what we have into a common base, and then
> provide strong semantics on each operation that encapsulates how we want each
> to operate (master ops should retry quickly, replication ops should retry
> slowly and give up eventually, etc), and also allow for testing of these
> intended implementations.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
