[
https://issues.apache.org/jira/browse/PHOENIX-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16035178#comment-16035178
]
James Taylor commented on PHOENIX-3907:
---------------------------------------
[~tdsilva] - this would be a nice one to get in since the JIRAs associated with
PHOENIX-3819 have been checked in. WDYT? Does this change make sense to you?
> Use LATEST_TIMESTAMP when UPDATE_CACHE_FREQUENCY is not zero
> ------------------------------------------------------------
>
> Key: PHOENIX-3907
> URL: https://issues.apache.org/jira/browse/PHOENIX-3907
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
>
> Currently with UPDATE_CACHE_FREQUENCY, we'll use LATEST_TIMESTAMP *most* of
> the time, until the cached entity expires, in which case we'll use the server
> timestamp. This seems a bit strange and inconsistent. We should instead
> always use LATEST_TIMESTAMP if UPDATE_CACHE_FREQUENCY is non zero, with the
> exception of the corner case for UPSERT SELECT and DELETE where the same
> table is being read and written to (see changes to FromCompiler for
> PHOENIX-3823).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
