[
https://issues.apache.org/jira/browse/HBASE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705665#action_12705665
]
Jonathan Gray commented on HBASE-32:
------------------------------------
Could also be interesting to have some kind of MR job that scanned over all
storefiles and generated aggregated statistics about all your tables and
regions.
A "quick" row count is certainly useful. A detailed report that could run
nightly would be very cool.
> [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
> 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.
