[PHOENIX-6541] Use ROW_TIMESTAMP column value as timestamps for conditional upsert mutations

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.16.1, 5.1.2
• Fix Version/s: 4.17.0, 5.2.0
• Assignee: Tanuj Khurana
• Reporter: Tanuj Khurana
• Created: 10/Sep/21 20:17
• Updated: 14/Sep/21 20:16
• Resolved: 14/Sep/21 20:16

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.  

Issue Links

• links to: GitHub Pull Request #1300