You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/01/27 17:00:00 UTC

[jira] [Updated] (HIVE-25900) Materialized view registry does not clean non existing views at refresh

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

ASF GitHub Bot updated HIVE-25900:
----------------------------------
    Labels: pull-request-available  (was: )

> Materialized view registry does not clean non existing views at refresh
> -----------------------------------------------------------------------
>
>                 Key: HIVE-25900
>                 URL: https://issues.apache.org/jira/browse/HIVE-25900
>             Project: Hive
>          Issue Type: Bug
>          Components: Materialized views
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> CBO plans of materialized views which are enabled for query rewrite are cached in HS2 (MaterializedViewsCache, HiveMaterializedViewsRegistry)
> The registry is refreshed periodically from HMS:
> {code:java}
> set hive.server2.materializedviews.registry.refresh.period=1500s;
> {code}
> This functionality is required when multiple HS2 instances are used in a cluster: MV drop operation is served by one of the HS2 instances and the registry is updated at that time in that instance. However other HS2 instances still cache the non-existent view and need to be refreshed by the updater thread.
> Currently the updater thread adds new entries, refresh existing ones but does not remove the outdated entries.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)