Hi folks, I know we don't want to "expose" the whole metadata tables in the REST api, but I would like to discuss adding metadata stats and metrics management. We are discussing this as part of the Apache Polaris TMS proposal.
The purpose is: 1. To add interfaces to manage metadata stats and metrics (partition stats, snapshot summaries, relay Parquet stats exposed via REST, ...) 2. The catalog implementation can deal with table properties, but can also extend to "extra" stats and metrics if needed 3. Query planners can use these metadata stats and metrics to perform better query plans. It could also be used by the server side planning to provide "pre-plan check" Before going to a proposal document, I would like to get first feedback from the community (if it makes sense or not). Thoughts ? Thanks ! Regards JB
