You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2023/08/01 05:58:00 UTC
[jira] [Updated] (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:all-tabpanel ]
Istvan Toth updated PHOENIX-6254:
---------------------------------
Priority: Major (was: Critical)
> 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: Major
>
> 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.10#820010)