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/08/25 18:54:20 UTC

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

James Taylor created PHOENIX-3209:
-------------------------------------

             Summary: 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
             Fix For: 4.9.0, 4.8.1


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)