You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Donghui Xu (JIRA)" <ji...@apache.org> on 2018/09/10 07:08:00 UTC
[jira] [Commented] (IMPALA-3681) Automatic invalidation of HMS
metadata using Hive replication API (HIVE-7973)
[ https://issues.apache.org/jira/browse/IMPALA-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16608807#comment-16608807 ]
Donghui Xu commented on IMPALA-3681:
------------------------------------
[~dtsirogiannis] Could you tell me what is the progress of this issue, or is there a development plan? Thanks.
> Automatic invalidation of HMS metadata using Hive replication API (HIVE-7973)
> -----------------------------------------------------------------------------
>
> Key: IMPALA-3681
> URL: https://issues.apache.org/jira/browse/IMPALA-3681
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog
> Affects Versions: Impala 2.6.0
> Reporter: Dimitris Tsirogiannis
> Priority: Minor
> Labels: catalog-server
>
> Hive is adding support for a replication API (https://issues.apache.org/jira/browse/HIVE-7973) that allows an HMS client to retrieve a global stream of HMS modifications made by all the HMS processes (in case of HMS HA). The Catalog server could use that API to automatically collect and update cached HMS metadata, thus eliminating the need for the user to call invalidate and refresh. This can only handle HMS metadata; file and block metadata will still need to be updated from the Namenode (e.g. by using inotify).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org