hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: Async Table API
Date Wed, 10 Jun 2015 17:27:36 GMT
On Wed, Jun 10, 2015 at 3:34 AM, Jurriaan Mous <jurmous@jurmo.us> wrote:
...

> >
> > The thinking on the above method is that if doing bulk checkAndMutate,
> that
> > they should all be inside a single row?
> That is correct. Although you can send out multiple requests to different
> rows at once with the Async api.
> > PromiseKeeper is a loaded term! See https://promisekeepers.org/#what ...
> > (smile)
> Ah I did not know since we don’t have those here. So it is better to
> rename? Any nice suggestions?
>

No. It is fine. It can be our little inside 'joke'.



> > > There will be a new AsyncResultScanner which handles incoming batches
> of
> > > result. It will not be possible to do next on it since this does not
> makes
> > > sense in an async context. There will be however a way to request a new
> > > batch with a promise.
> > >
> > >
> > I like this.... no next. What you thinking as means of specifying
> > 'batches'? We've been trying to move away from specifying batches in
> terms
> > of row count to instead do batches of a particular size (See
> HBASE-13441).
> As I currently implemented them you can request nextBatch promises until
> isClosed() is true. So if batches are based on size in the future it is
> easy to change the internals.
>
> Grand.

St.Ack

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message