Uploaded image for project: 'Phoenix'
  1. Phoenix
  2. PHOENIX-6541

Use ROW_TIMESTAMP column value as timestamps for conditional upsert mutations

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 4.16.1, 5.1.2
    • 4.17.0, 5.2.0
    • None
    • None

    Description

      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.  

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            tkhurana Tanuj Khurana
            tkhurana Tanuj Khurana
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment