[
https://issues.apache.org/jira/browse/PHOENIX-3209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
James Taylor updated PHOENIX-3209:
----------------------------------
Issue Type: Sub-task (was: Bug)
Parent: PHOENIX-3819
> Ensure scans run at specific server timestamp for UPSERT SELECT to same table
> -----------------------------------------------------------------------------
>
> Key: PHOENIX-3209
> URL: https://issues.apache.org/jira/browse/PHOENIX-3209
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Fix For: 4.11.0
>
>
> There's likely a potential issue lurking if UPDATE_CACHE_FREQUENCY is set on
> a table and an UPSERT SELECT is performed to update the same table. In this
> case, we need to run the SELECT and the UPSERT at a particular timestamp to
> prevent the SELECT from seeing the new rows being upsert. This may not be the
> case if UPDATE_CACHE_FREQUENCY is set.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
