Thanks all for your insights into this.
I would agree that providing mechanisms to support no-outage upgrades going
forward would really be widely beneficial. I was looking forward to Avro for
this reason.
Some follow up questions:
1) If asynchbase client to do this (i.e. talk wire protocol and
On Sun, Mar 6, 2011 at 9:25 PM, Suraj Varma svarma...@gmail.com wrote:
Thanks all for your insights into this.
I would agree that providing mechanisms to support no-outage upgrades going
forward would really be widely beneficial. I was looking forward to Avro for
this reason.
Some follow up
So when you look at the interface that the client uses to talk to the
regionservers it has calls like this:
public R MultiResponse multi(MultiActionR multi) throws IOException;
public long openScanner(final byte [] regionName, final Scan scan)
throws IOException;
etc
Note that this is the
On Sun, Mar 6, 2011 at 9:25 PM, Suraj Varma svarma...@gmail.com wrote:
1) If asynchbase client to do this (i.e. talk wire protocol and adjust based
on server versions), why not the native hbase client? Is there something in
the native client design that would make this too hard / not worth
