[
https://issues.apache.org/jira/browse/PHOENIX-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16184822#comment-16184822
]
James Taylor commented on PHOENIX-4187:
---------------------------------------
Thanks, [~tdsilva]. So for the change below, does that mean that the row
timestamp value won't change until the cache entry expires?
{code}
+ (table.getRowTimestampColPos() == -1 &&
connection.getMetaDataCache().getAge(tableRef) <
table.getUpdateCacheFrequency() ))) {
{code}
I was thinking we should always hit the server when we need the value for row
timestamp (regardless of the UPDATE_CACHE_FREQUENCY setting).
> 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: Thomas D'Silva
> Fix For: 4.12.0
>
> Attachments: PHOENIX-4187.patch, PHOENIX-4187-v2-master.patch,
> PHOENIX-4187-v2.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
