Hi Yong, I think this topic is becoming increasingly important, especially as the event persistence layer is being extended to support a broader range of events (https://github.com/apache/polaris/pull/4225). In my opinion, the best approach would be to allow Polaris users to configure an automated cleanup process and provide a REST API for managing the scheduling and configuration of these cleanup tasks.
Nandor Yong Zheng <[email protected]> ezt írta (időpont: 2026. jún. 7., V, 20:34): > 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 >
