[
https://issues.apache.org/jira/browse/HBASE-9049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14941883#comment-14941883
]
Jesse Yates commented on HBASE-9049:
------------------------------------
Thinking about this.. it seems like we might want to keep the class around in
the interest of utility for users. If we do, then it should have some sort of
docs (even if just minimal) XOR we throw out the class. Yes, its a simple class
and anyone could rewrite it, but this saves everyone from rewriting it.
I dunno, maybe ppl don't need it? Or the PMC wants a slimmer codebase? What say
you mr. [~stack]?
> Generalize ServerCallable creation to support custom callables
> --------------------------------------------------------------
>
> Key: HBASE-9049
> URL: https://issues.apache.org/jira/browse/HBASE-9049
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0, 0.95.2, 0.94.11
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Attachments: hbase-9049-trunk-v0.patch, hbase-9049-trunk-v1.patch,
> hbase-9049-trunk-v2.patch, hbase-9049-trunk-v3.patch,
> hbase-9049-trunk-v4.patch
>
>
> Currently, sever callables are instantiated via direct calls. Instead, we can
> use a single factory and that allows more specialized callable
> implementations, for instance, using a circuit-breaker pattern (or the
> Hystrix implementation!) to minimize attempts to contact the server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
