zhangshenghang commented on issue #10329: URL: https://github.com/apache/seatunnel/issues/10329#issuecomment-3754425404
<!-- code-pr-reviewer --> Thanks for proposing this feature. The issue is valid: current IMap file storage (`IMapFileStorage`, `CloudWriter`, `HdfsWriter`) uses append-only writes without cleanup, causing unlimited storage growth for high-frequency IMaps like `engine_runningJobMetrics`. `WALReader` only merges data in-memory without physically deleting old files. To design a compaction mechanism effectively, please clarify: 1. Preferred default trigger strategy (time-based/file-count/file-size thresholds)? 2. Should manual triggering be supported (REST API/CLI)? 3. Any performance tolerance limits for compaction during job execution? Potential starting points: - `seatunnel-engine/seatunnel-engine-storage/imap-storage-plugins/imap-storage-file/src/main/java/org/apache/seatunnel/engine/imap/storage/file/IMapFileStorage.java` - add `compact()` and scheduled compaction task - `seatunnel-engine/seatunnel-engine-storage/imap-storage-plugins/imap-storage-file/src/main/java/org/apache/seatunnel/engine/imap/storage/file/common/FileConstants.java` - add compaction config constants - `seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/SeaTunnelServer.java` - add REST API endpoint -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
