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

Posted to issues@phoenix.apache.org by "Kadir Ozdemir (Jira)" <ji...@apache.org> on 2022/06/10 23:32:00 UTC

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

    [ https://issues.apache.org/jira/browse/PHOENIX-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17553000#comment-17553000 ] 

Kadir Ozdemir commented on PHOENIX-6254:
----------------------------------------

It is not clear what improvement is suggested here. Also it would be helpful if the latency or throughput impact for ROW_TIMESTAMP is measured and provided here.

> 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
>            Priority: Critical
>
> 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.20.7#820007)