You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/09/10 19:58:20 UTC

[jira] [Updated] (PHOENIX-3209) Ensure scans run at latest server timestamp for UPSERT SELECT to same table

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

James Taylor updated PHOENIX-3209:
----------------------------------
    Fix Version/s:     (was: 4.8.1)
                       (was: 4.9.0)

> Ensure scans run at latest server timestamp for UPSERT SELECT to same table
> ---------------------------------------------------------------------------
>
>                 Key: PHOENIX-3209
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-3209
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: James Taylor
>
> 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.4#6332)