You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Chinmay Kulkarni (Jira)" <ji...@apache.org> on 2019/12/21 00:58:04 UTC
[jira] [Closed] (PHOENIX-5403) Optimize metadata cache lookup of
global tables using a tenant specific connection
[ https://issues.apache.org/jira/browse/PHOENIX-5403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chinmay Kulkarni closed PHOENIX-5403.
-------------------------------------
Bulk closing Jiras for the 4.15.0 release.
> Optimize metadata cache lookup of global tables using a tenant specific connection
> ----------------------------------------------------------------------------------
>
> Key: PHOENIX-5403
> URL: https://issues.apache.org/jira/browse/PHOENIX-5403
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.14.2
> Reporter: Thomas D'Silva
> Assignee: Thomas D'Silva
> Priority: Major
> Fix For: 4.15.0, 5.1.0
>
> Attachments: PHOENIX-5403-v2.patch, PHOENIX-5403-v3.patch, PHOENIX-5403-v4.patch, PHOENIX-5403-v5.patch, PHOENIX-5403.patch, diff.patch
>
>
> If we use a teanant specific connection to look up a global table we always make an rpc to the server even if the UPDATE_CACHE_FREQUENCY is set on the table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)