bruary 12, 2018 11:59 AM > To: user@hbase.apache.org > Subject: Re:
Inconsistent rows exported/counted when looking at a set, > unchanged past time
frame. > > Hi Andrew, > > Yes. The answer is, of course, that you should see
consistent results from > HBase if there are no mutatio
t; the clue!
>
> Andrew Kettmann
> Consultant, Platform Services Group
>
> -Original Message-
> From: Josh Elser [mailto:els...@apache.org]
> Sent: Monday, February 12, 2018 11:59 AM
> To: user@hbase.apache.org
> Subject: Re: Inconsistent rows exported/counted wh
org]
Sent: Monday, February 12, 2018 11:59 AM
To: user@hbase.apache.org
Subject: Re: Inconsistent rows exported/counted when looking at a set,
unchanged past time frame.
Hi Andrew,
Yes. The answer is, of course, that you should see consistent results from
HBase if there are no mutations in fli
-cdh5.8.0
HDFS/YARN: Hadoop 2.6.0-cdh5.8.0
Andrew Kettmann
Consultant, Platform Services Group
-Original Message-
From: Josh Elser [mailto:els...@apache.org]
Sent: Monday, February 12, 2018 11:59 AM
To: user@hbase.apache.org
Subject: Re: Inconsistent rows exported/counted when looking
Hi Andrew,
Yes. The answer is, of course, that you should see consistent results
from HBase if there are no mutations in flight to that table. Whether
you're reading "current" or "back-in-time", as long as you're not
dealing with raw scans (where compactions may persist delete
tombstones),
A simpler question would be this:
Given:
* a set timeframe in the past (2-3 days roughly a year ago)
* we are NOT removing records from the table at all
* We ARE inserting into this table actively
Should I expect two consecutive runs of the rowcounter mapreduce job to return
an
