[
https://issues.apache.org/jira/browse/HBASE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994018#comment-12994018
]
Andrew Purtell commented on HBASE-3523:
---------------------------------------
- Run time interface extension, consider the existing dynamic RPC stuff though
it doesn't have to be done exactly that way. Regarding use (or not) of proxy
objects, right now we have <T> HTable.coprocessorProxy(...) which if users
adopt will produce user code that does need it.
- Option for async interaction.
- Use executors instead of threads. Allow the user to pass in an executor pool
of desired construction.
- Resurrect HBASE-1015?
> Rewrite our client
> ------------------
>
> Key: HBASE-3523
> URL: https://issues.apache.org/jira/browse/HBASE-3523
> Project: HBase
> Issue Type: Brainstorming
> Reporter: stack
>
> Is it just me or do others sense that there is pressure building to redo the
> client? If just me, ignore the below... I'll just keep notes in here.
> Otherwise, what would the requirements for a client rewrite look like?
> + Let out InterruptedException
> + Enveloping of messages or space for metadata that can be passed by client
> to server and by server to client; e.g. the region a.b.c moved to server
> x.y.z. or scanner is finished or timeout
> + A different RPC? One with tighter serialization.
> + More sane timeout/retry policy.
> Does it have to support async communication? Do callbacks?
> What else?
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
