You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2020/10/24 09:33:00 UTC

[jira] [Updated] (PHOENIX-6192) UpgradeUtil.syncUpdateCacheFreqAllIndexes() does not use tenant-specific connection to resolve tenant views

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

Viraj Jasani updated PHOENIX-6192:
----------------------------------
    Attachment: PHOENIX-6192.4.x.000.patch

> UpgradeUtil.syncUpdateCacheFreqAllIndexes() does not use tenant-specific connection to resolve tenant views
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-6192
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6192
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 5.0.0, 4.15.0
>            Reporter: Chinmay Kulkarni
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 5.1.0, 4.16.0
>
>         Attachments: PHOENIX-6192.4.x.000.patch
>
>
> In UpgradeUtil.synchUpdateCacheFreqAllIndexes(), we try to retrieve all child views of each table to make all the view index UPDATE_CACHE_FREQUENCY property values in sync with the view.
> Here however, when iterating over the parent->child link results, we don't use a tenant-specific connection to retrieve a tenant view leading to the PTable resolution failing (see [this|https://github.com/apache/phoenix/blob/264310bd1e6c14996c3cfb11557fc66a012cb01b/phoenix-core/src/main/java/org/apache/phoenix/util/UpgradeUtil.java#L1369])



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