[ 
https://issues.apache.org/jira/browse/PHOENIX-3907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

James Taylor updated PHOENIX-3907:
----------------------------------
    Description: For non transactional tables, 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. Instead (for non transactional tables), 
we should 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).  (was: 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).)

> 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
>
> For non transactional tables, 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. Instead (for non transactional tables), we should 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)

Reply via email to