Hello,

A while back Alex raised https://github.com/apache/polaris/issues/2573 for 
requesting a mechanism to purge the events table. Recently there is a persisted 
iceberg metrics also got introduced 
(https://github.com/apache/polaris/pull/3385) and this created two tables (read 
and write metrics tables) which we also lack the life cycle management and 
tables size should grow indefinitely. We will likely need a mechanism to handle 
both.

I am wondering what does community thinks about this? Should this be part of 
admin tool where admins/ops should make the call on when to clean up or should 
we have a janitor process that runs automatically (users will need to provide 
rules on what to cleanup such as time based TTL).

Thanks,
Yong Zheng  

Reply via email to