Juan Yu created IMPALA-6531:
-------------------------------
Summary: Keep history of Metadata operations happened before
calling "invalidate metadata"
Key: IMPALA-6531
URL: https://issues.apache.org/jira/browse/IMPALA-6531
Project: IMPALA
Issue Type: Improvement
Reporter: Juan Yu
Catalog webUI now can show the cost of table metadata now. Yeah.
including top tables with high memory usage
top table with high metadata ops (refresh, alter, etc.)
However the metadata ops count is reset if "invalidate metadata <table>" is
called.
This is because catalog creates a new object for the table metadata after
"invalidate metadata".
Could we add a unique ID per table? so the metadata ops history can be kept?
Note in the scenario of drop and recreate a table with the same name, it still
considers as a different table.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
