Ya thanks Ram. With VERSIONS => 1 it means max versions? If yes, why should
the old value be stored when there is a latest version.
Thanks
Regards
Mukund Murrali
On Fri, Oct 16, 2015 at 1:40 PM, ramkrishna vasudevan <
ramkrishna.s.vasude...@gmail.com> wrote:
> With VERSIONS=>1 and MIN_VERSIONS=
With VERSIONS=>1 and MIN_VERSIONS=0, I think the intended behaviour is to
always have the current version as the one to be returned. So in your cases
you inserted two cells at different timestamp. But the Delete with
addColumn will always try to delete the latest version. So in this case
the lates
Can anyone enlighten why this is happening. This is causing problems in our
production.
On Thu, Oct 15, 2015 at 4:15 PM, mukund murrali
wrote:
> Hi
>
> I am using hbase-1.0. I had two column families C1 and C2.
>
> C1 => 'VERSIONS => 1, MIN_VERSIONS => 0 (default)
> C2 => 'VERSIONS' => 1, MIN_VE
Hi
I am using hbase-1.0. I had two column families C1 and C2.
C1 => 'VERSIONS => 1, MIN_VERSIONS => 0 (default)
C2 => 'VERSIONS' => 1, MIN_VERSIONS => 1
I inserted two versions as follows
put 'test','ro1','C1:col1,'value1'
put 'test','ro1','C2:col1,'value1'
put 'test','ro1','C1:col1,'value2'
p
