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 "Quanlong Huang (Jira)" <ji...@apache.org> on 2019/09/24 01:07:00 UTC
[jira] [Commented] (IMPALA-7506) Support global INVALIDATE METADATA
on fetch-on-demand impalad
[ https://issues.apache.org/jira/browse/IMPALA-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936284#comment-16936284 ]
Quanlong Huang commented on IMPALA-7506:
----------------------------------------
I think this can be implemented by propagating the catalog version when we reset the catalog. It's a lower bound for the min catalog version. If this is right, the implementation will be simple. Wrote down my understanding on the relative metadata stuff with the implementation design: [https://docs.google.com/document/d/1-AoigzsQPgSGosW4vtVP8E7TiwoJJfLkAq3Rd6KvKBg/edit?usp=sharing]
[~tlipcon], [~bharathv], could you help to have a look on it?
> Support global INVALIDATE METADATA on fetch-on-demand impalad
> -------------------------------------------------------------
>
> Key: IMPALA-7506
> URL: https://issues.apache.org/jira/browse/IMPALA-7506
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Todd Lipcon
> Assignee: Quanlong Huang
> Priority: Major
> Labels: catalog-v2
>
> There is some complexity with how this is implemented in the original code: it depends on maintaining the minimum version of any object in the impalad's local cache. We can't determine that in an on-demand impalad, so INVALIDATE METADATA is not supported currently on "fetch-on-demand".
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org