You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Geoffrey Jacoby (Jira)" <ji...@apache.org> on 2021/09/14 20:17:00 UTC

[jira] [Resolved] (PHOENIX-6541) Use ROW_TIMESTAMP column value as timestamps for conditional upsert mutations

     [ https://issues.apache.org/jira/browse/PHOENIX-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Geoffrey Jacoby resolved PHOENIX-6541.
--------------------------------------
    Fix Version/s: 5.2.0
                   4.17.0
       Resolution: Fixed

Merged to 4.x and cherry-picked to master

> Use ROW_TIMESTAMP column value as timestamps for conditional upsert mutations
> -----------------------------------------------------------------------------
>
>                 Key: PHOENIX-6541
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6541
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.16.1, 5.1.2
>            Reporter: Tanuj Khurana
>            Assignee: Tanuj Khurana
>            Priority: Major
>             Fix For: 4.17.0, 5.2.0
>
>
> For tables without indexes if ROW_TIMESTAMP is specified in the table DDL, the mutations generated by conditional upserts don't have the correct timestamp. This was introduced as part of PHOENIX-6387
> For tables with indexes, Phoenix doesn't allow specifying a PK column as ROW_TIMESTAMP so this bug doesn't apply. This Jira aims to restore parity with the old behavior of conditional upserts with regards to ROW_TIMESTAMP.  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)