hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Enis Söztutar <enis....@gmail.com>
Subject Re: HBase wire compatibility
Date Sat, 18 Feb 2012 01:30:50 GMT
While working on keeping bw compatibility for
https://issues.apache.org/jira/browse/HBASE-5371, I realized that it might
be a good idea to include the co-processor interfaces into the scope as
well. Although they are marked as advanced API's, and even if you wrap them
under some java class, there will be need to access the functionality from
clients, and they should be treated the same way as 3 and 4. Just something
to consider until Thursday, I'll try to be there as well.


On Thu, Feb 16, 2012 at 4:54 PM, Stack <stack@duboce.net> wrote:

> On Thu, Feb 16, 2012 at 3:55 PM, Jeff Whiting <jeffw@qualtrics.com> wrote:
> > What I'm suggesting may not be possible but it seems like it is worth
> > keeping in mind through the design and implementation process.
> >
> There is already proof that what you suggest is possible.  asynchbase
> is a 'lighter', 'incomplete' but
> complete-enough-for-a-particular-purpose client that does much of what
> you talk of except the bit about being in another language.
> St.Ack

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