hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stack <st...@duboce.net>
Subject Re: [UPDATE] Finishing up 0.96 --> WAS Re: 0.95 and 0.96 remaining issues
Date Wed, 31 Jul 2013 17:31:09 GMT
On Wed, Jul 31, 2013 at 9:55 AM, Nick Dimiduk <ndimiduk@gmail.com> wrote:

> On Tue, Jul 30, 2013 at 9:38 PM, James Taylor <jtaylor@salesforce.com
> >wrote:
>
> > So row key order won't match the natural sort order?
> >
>
> With the "Legacy" types that are based on Bytes, you get whatever you get.
> Strings and pass-through byte[]'s work like normal; positive integers will
> work, but not negatives; &c. HBase would not ship out-of-the-box with
> general purpose order-preserving types, but you'd have the API and be able
> to implement your own.
>
>
So what would be the incentive using the new API be?

And then when the implementation changes -- it serializes in sort-order --
will it confuse?

Thanks Nick,
St.Ack

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