phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samarth Jain (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-4187) Use server timestamp for ROW_TIMESTAMP column when value is not specified
Date Wed, 27 Sep 2017 23:04:00 GMT

    [ https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183402#comment-16183402
] 

Samarth Jain commented on PHOENIX-4187:
---------------------------------------

[~tdsilva] - we shouldn't be using CURRENT_SCN when doing UPSERTS since we are planning on
making connections with CURRENT_SCN read only. Instead, we can control the timestamp ourself
by using the EnvironmentEdgeManager class that James mentioned. This way, we can control the
value of row_timestamp column when it is not specified in the upsert. It will then make the
test of querying for the exact rowtimestamp value deterministic too.

> Use server timestamp for ROW_TIMESTAMP column when value is not specified
> -------------------------------------------------------------------------
>
>                 Key: PHOENIX-4187
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4187
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Samarth Jain
>            Assignee: Thomas D'Silva
>             Fix For: 4.12.0
>
>         Attachments: PHOENIX-4187.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message