phoenix-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ankit Singhal <ankitsingha...@gmail.com>
Subject Re: ROW_TIMESTAMP weird behaviour
Date Tue, 07 Feb 2017 09:58:31 GMT
I think you are also hitting
https://issues.apache.org/jira/browse/PHOENIX-3176.

On Tue, Feb 7, 2017 at 2:18 PM, Dhaval Modi <dhavalmodi24@gmail.com> wrote:

> Hi Pedro,
>
> Upserted key are different. One key is for July month & other for January
> month.
> 1. '2017-*07*-02T15:02:21.050'
> 2. '2017-*01*-02T15:02:21.050'
>
>
> Regards,
> Dhaval Modi
> dhavalmodi24@gmail.com
>
> On 7 February 2017 at 13:18, Pedro Boado <pedro.boado@gmail.com> wrote:
>
>> Hi.
>>
>> I don't think it's weird. That column is PK and you've upserted twice the
>> same key value so first one is inserted and second one is updated.
>>
>> Regards.
>>
>>
>>
>> On 7 Feb 2017 04:59, "Dhaval Modi" <dhavalmodi24@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I am facing abnormal scenarios with ROW_TIMESTAMP.
>>>
>>> I created table in Phoenix as below:
>>> CREATE TABLE DUMMY(XXX_TS TIMESTAMP NOT NULL CONSTRAINT pk PRIMARY KEY
>>> (XXX_TS ROW_TIMESTAMP))
>>> where "XXX_TS" is used as ROW_TIMESTAMP.
>>>
>>> Now, I am trying to add data:
>>> upsert into DUMMY values('2017-07-02T15:02:21.050');
>>> upsert into DUMMY values('2017-01-02T15:02:21.050');
>>>
>>> I am only seeing one entry.
>>> *======================================================*
>>> *0: jdbc:phoenix:> select * from DUMMY;*
>>> *+--------------------------+*
>>> *|          XXX_TS          |*
>>> *+--------------------------+*
>>> *| 2017-01-02 15:02:21.050  |*
>>> *+--------------------------+*
>>> *1 row selected (0.039 seconds)*
>>> *======================================================*
>>>
>>>
>>> Additional info:
>>> System date of HBase & Phoenix: mar feb  7 05:57:37 CET 2017
>>>
>>>
>>> Regards,
>>> Dhaval Modi
>>> dhavalmodi24@gmail.com
>>>
>>
>

Mime
View raw message