Hi Yong, Thanks for starting this discussion!
>From my POV the Admin tool does look like a good fit for this capability. It is similar to the NoSQL maintenance task [3395]. I believe end users could then schedule the maintenance runs according to their deployment mechanics, e.g. via k8s jobs. I made an attempt at refactoring the Admin CLI for pluggability in terms of sub-commands in [3947]. We could revive that PR if there's community interest. The Metrics / Events maintenance tasks could then be plugged in similarly to NoSQL maintenance. [3395] https://github.com/apache/polaris/pull/3395 [3947] https://github.com/apache/polaris/pull/3947 Cheers, Dmitri. On Sun, Jun 7, 2026 at 2:34 PM Yong Zheng <[email protected]> wrote: > 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 >
