[jira] [Resolved] (HBASE-3523) Rewrite our client (client 2.0)

["Andrew Purtell (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Purtell resolved HBASE-3523.
-----------------------------------
    Resolution: Not A Problem

> Rewrite our client (client 2.0)
> -------------------------------
>
>                 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 was sent by Atlassian JIRA
(v6.3.4#6332)