You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/04/24 00:53:21 UTC
[jira] Resolved: (HBASE-32) [hbase] Add row count estimator
[ https://issues.apache.org/jira/browse/HBASE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-32.
------------------------
Resolution: Fixed
Fix Version/s: 0.2.0
This was committed to branch and trunk
> [hbase] Add row count estimator
> -------------------------------
>
> Key: HBASE-32
> URL: https://issues.apache.org/jira/browse/HBASE-32
> Project: Hadoop HBase
> Issue Type: New Feature
> Components: client
> Reporter: stack
> Priority: Minor
> Fix For: 0.2.0
>
> Attachments: 2291_v01.patch, Keying.java
>
>
> Internally we have a little tool that will do a rough estimate of how many rows there are in a dataHbase. It keeps getting larger and larger partitions running scanners until it turns up > N occupied rows. Once it has a number > N, it multiples by the partition size to get an approximate row count.
> This issue is about generalizing this feature so it could sit in the general hbase install. It would look something like:
> {code}
> long getApproximateRowCount(final Text startRow, final Text endRow, final long minimumCountPerPartition, final long maximumPartitionSize)
> {code}
> Larger minimumCountPerPartition and maximumPartitionSize values would make the count more accurate but would mean the method ran longer.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.