[jira] [Created] (HBASE-15194) TestStochasticLoadBalancer.testRegionReplicationOnMidClusterSameHosts flaky on trunk

stack created HBASE-15194: - Summary: TestStochasticLoadBalancer.testRegionReplicationOnMidClusterSameHosts flaky on trunk Key: HBASE-15194 URL: https://issues.apache.org/jira/browse/HBASE-15194 Project:

[jira] [Resolved] (HBASE-15194) TestStochasticLoadBalancer.testRegionReplicationOnMidClusterSameHosts flaky on trunk

[ https://issues.apache.org/jira/browse/HBASE-15194?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] stack resolved HBASE-15194. --- Resolution: Fixed Assignee: stack Pushed to master >

When split a region, how to get row keys efficiently instead of using midkey

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

Re: When split a region, how to get row keys efficiently instead of using midkey

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 wrote: > Hi, > > In default region split

Successful: HBase Generate Website

Build status: Successful If successful, the website and docs have been generated. If failed, skip to the bottom of this email. Use the following commands to download the patch and apply it to a clean branch based on origin/asf-site. If you prefer to keep the hbase-site repo around