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

Posted to dev@phoenix.apache.org by "Tanuj Khurana (Jira)" <ji...@apache.org> on 2023/01/23 20:15:00 UTC

[jira] [Assigned] (PHOENIX-6860) Multiple calls for the same table to ConnectionQueryServicesImpl#getTable within the execution of the same statement

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

Tanuj Khurana reassigned PHOENIX-6860:
--------------------------------------

    Assignee: Kadir OZDEMIR

> Multiple calls for the same table to ConnectionQueryServicesImpl#getTable within the execution of the same statement
> --------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-6860
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6860
>             Project: Phoenix
>          Issue Type: Improvement
>    Affects Versions: 5.1.2, 5.1.3
>            Reporter: Tanuj Khurana
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>
> For some statements like for example UPSERT statements, we make multiple calls to ConnectionQueryServicesImpl#getTable() for the same table like once in FromCompiler when creating the table ref and again when sending mutations in MutationState#validateAndGetServerTimestamp(). I think we can reduce the unnecessary RPCs to the server if we have already resolved the table for a given statement.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)