hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: Hbase data version performance impact
Date Tue, 31 Jan 2017 18:55:36 GMT
For #3, you need to retrieve multiple versions (to get to V2).

Take a look at TestVisibilityLabelsWithDeletes#testDeleteColumnWithLatestTimeStampUsingMultipleVersions
around line 1368.

FYI

On Tue, Jan 31, 2017 at 9:58 AM, Manjeet Singh <manjeet.chandhok@gmail.com>
wrote:

> Hi All
>
> can anyone tell me what is the Impact of using Hbase data version
>
> Q1 what is the impact if I have 1000 version set or what if its 10000
>
> Q2 Is it good idea to put non default version in different column family?
>
>
> Q3 Does version support to get specific version value?
>  as showing below I want to use only A2
> rk header header2
> 001 A1 V1
> 001 A2 V2
> 001 A3 V3
>
> Q4 Any idea to use concept of Nested table in Hbase? I am considering
> version
>
>
> Thanks
> Manjeet
>
>
>
> --
> luv all
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message