hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: When split a region, how to get row keys efficiently instead of using midkey
Date Sat, 30 Jan 2016 15:18:40 GMT
bq. get all row keys in a range

Currently there is no metadata in HFile w.r.t. all row keys which appear in
the HFile.
As you have found out, there is no fast way of getting such information.

On Fri, Jan 29, 2016 at 9:41 PM, onealbao <onealbao@gmail.com> wrote:

> Hi,
> In default region split policy, it first finds largest stores, then finds
> largest store files, and finally get split point (midkey) of the largest
> store file. Is there anyway to efficiently get all row-keys of a store
> files? I tried to use ResultScanner with setting start/end row key, but I
> found the time consumption of scan (scan execution and read scan record) is
> at least 100 times (100 ms) slower than directly get midkey (1 ms).
> Actually, I just want to get all row keys in a range, and I would like to
> use my own policy to group some row keys together. Since all data in my
> table has similar size. Any suggestion is appreciated.
> --
> View this message in context:
> http://apache-hbase.679495.n3.nabble.com/When-split-a-region-how-to-get-row-keys-efficiently-instead-of-using-midkey-tp4077492.html
> Sent from the HBase Developer mailing list archive at Nabble.com.

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