phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Samarth Jain <samarth.j...@gmail.com>
Subject Re: Phoenix4.2.1 against HBase0.98.6 encountered a strange problem when using connection with props
Date Thu, 04 Dec 2014 09:10:43 GMT
The value of timestamp provided by CURRENT_SCN_ATTRIBUTE has to be greater
than the table timestamp. So it really is any arbitrary value >= table
create timestamp. Providing timestamps on connections helps us with
executing point in time or snapshot queries. In other words, it's a way of
surfacing the time dimension of rows in HBase. So if you have two rows -
one inserted at time t1 and the other inserted at time t2:

Setting scn time < t1 (but greater than table create timestamp) - you will
see both rows t1 and t2.
for t1 < scn time < t2 - you will only see t2
for t1 < t2 < scn time - you won't see either t1 or t2.

Hope this helps.

On Thu, Dec 4, 2014 at 12:54 AM, chenwenhui <c77_cn@163.com> wrote:

> In deed, i want to test CURRENT_SCN_ATTRIBUTE.
> It looks like that the root reason is caused by the value for CURRENT_SCN_ATTRIBUTE.
> If the value is less than the time to create table, then produce  the
> exception, otherwise, all things become okay. i.e. the arbitrary timestamp
> can not be less than the create table time.
> If so, the timestamp can not be called arbitrary, What is the design
> purpose?
>
>
>

Mime
View raw message