[
https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samarth Jain resolved PHOENIX-4187.
-----------------------------------
Resolution: Fixed
Turns out this is not an issue. When we don't use the server timestamp, we end
up using HConstants.LATEST_TIMESTAMP. In such a case, HBase intercepts those
mutations and changes the timestamp from LATEST_TIMESTAMP to the current time
on the server.
> 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: Samarth Jain
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
