[
https://issues.apache.org/jira/browse/IMPALA-6531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Quanlong Huang updated IMPALA-6531:
-----------------------------------
Parent: (was: IMPALA-6581)
Issue Type: New Feature (was: Sub-task)
> 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: New Feature
> Components: Catalog
> Reporter: Juan Yu
> Priority: Major
>
> 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
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
