Yet another approach is to transform your keys into byte comparable values
that preserve your desired sort order, and store that instead. The ICU
library has the ability to do this for various collations of UTF strings:
http://userguide.icu-project.org/collation/architecture#TOC-Sort-Keys
So for
Zoltan,
It's actually a bit more complicated because the behavior is
non-deterministic. If a compaction happens the delete marker may be
removed, and if you add the rows back after this time they *will* be
visible. See the following for more info:
http://mail-archives.apache.org/mod_mbox/hbase-de
Lin,
Looks like your questions may already be answered, but you might find the
following link comparing "traditional" columnar databases against
HBase/BigTable interesting:
http://dbmsmusings.blogspot.com/2010/03/distinguishing-two-major-types-of_29.html
-Jason
On Sun, Aug 5, 2012 at 8:03 PM, L
Abhishek,
Setting your column family's bloom filter to ROWCOL will include qualifiers:
http://hbase.apache.org/book.html#schema.bloom
-Jason
On Wed, Aug 22, 2012 at 1:49 PM, Pamecha, Abhishek wrote:
> Can I enable bloom filters per block at column qualifier levels too? That
> way, will small
On Tue, Jan 24, 2012 at 11:45 AM, Praveen Sripati
wrote:
> Thanks for the response. I am just getting started with HBase. And before
> getting into the code/api level details, I am trying to understand the
> problem area HBase is trying to address through it's architecture/design.
>
> 1) So, what
