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

Posted to dev@phoenix.apache.org by "siaron (Jira)" <ji...@apache.org> on 2020/12/09 12:47:00 UTC

[jira] [Created] (PHOENIX-6254) Does ROW_TIMESTAMP conflict with UPDATE_CACHE_FREQUENCY?

siaron created PHOENIX-6254:
-------------------------------

             Summary: Does ROW_TIMESTAMP conflict with UPDATE_CACHE_FREQUENCY? 
                 Key: PHOENIX-6254
                 URL: https://issues.apache.org/jira/browse/PHOENIX-6254
             Project: Phoenix
          Issue Type: Improvement
          Components: core
    Affects Versions: 5.0.0
            Reporter: siaron
             Fix For: 5.1.0


If the table has a primary key column as `ROW_TIMESTAMP`. When `upsert` calls `org.apache.phoenix.execute.MutationState#validateAndGetServerTimestamp`, it will keep RPC requesting the server side. This leads to a decrease in write performance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)