Maxwell Guo created IMPALA-12468:
------------------------------------
Summary: Add the ability to update EventProcessorStatus
Key: IMPALA-12468
URL: https://issues.apache.org/jira/browse/IMPALA-12468
Project: IMPALA
Issue Type: Improvement
Components: be, Catalog, fe
Reporter: Maxwell Guo
Assignee: Maxwell Guo
Once the impala and hive's status is missmatched , and the EventProcessorStatus
become NEED_INVALIDATEļ¼ we usually use invalidate metadata to reset the catalog
instance. And then impala will update the status to ACTIVE .
But if impala contains many tables , the cost of invalidate is a bit high for a
global invalidate. So we may invalidate metadata for tables one by one for
these incremental changed table. For example , we have 1000,000,000,000 tables
but only some of the table event process occurs CatalogException and
MetastoreNotificationNeedsInvalidateException was thrown. I think there is no
need to invalidate all table caches.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
