tarted..
>
>Results are expected to be deterministic in normal scenarios. can
> you elaborate what is the difference you see after HBase restarted?
>
> bq. SELECT SUM(GUIDE_POSTS_ROW_COUNT) from SYSTEM.STATS WHERE
> PHYSICAL_NAME = 'MYTABLE';
>
> We calculate row count till the
ct: Re: Efficient way to get the row count of a table
The count would change when a major compaction is done. Back in 4.7, it may
have changed when a split occurs too (but this is no longer the case). I'd
recommend moving to a newer version: 4.7 was release almost two years ago and
is six releases bac
apache.org/apidocs/org/apache/hadoop/hbase/mapreduce/RowCounter.html>
> http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/
> mapreduce/RowCounter.html M/R.
>
> On Tue, Dec 19, 2017 at 3:18 PM, James Taylor <jamestay...@apache.org>
> wrote:
>
>> If it needs to
he only way. If
your data is write-once data, you might be able to track the row
count at the application level through some kind of atomic counter
in a different table (but this will likely be brittle). If you can
live with an estimate, you could enable statistics [1], optionally
ur
> data is write-once data, you might be able to track the row count at the
> application level through some kind of atomic counter in a different table
> (but this will likely be brittle). If you can live with an estimate, you
> could enable statistics [1], optionally configuring Phoen
If it needs to be 100% accurate, then count(*) is the only way. If your
data is write-once data, you might be able to track the row count at the
application level through some kind of atomic counter in a different table
(but this will likely be brittle). If you can live with an estimate, you
could
Hi,
Is there a way to get the total row count of a phoenix table without
running select count(*) from table ?
my use case is to monitor the record count in a table every x minutes,
so didn't want to put load on the system by running a select count(*)
query.
Thanks,
Jins George
= 'MYTABLE';
We calculate row count till the guidePosts is found in the region
and no count will be stored for a region having a size not enough for
guidepost width or remaining region after the last guidePosts. so this
row_count should not be used against actual count.
On Wed, Sep 13, 2017 at 4:04
