lxy-9602 opened a new issue, #571: URL: https://github.com/apache/paimon-cpp/issues/571
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon-cpp/issues) and found nothing similar. ### Motivation Fixed-bucket append tables with deletion vectors currently do not support automatically triggering compaction based on deleted-row counts or deletion ratios. The built-in automatic strategy selects files based on file count and size, so files with substantial deletions may remain uncompacted when those conditions are not met. A custom compaction API would allow external planners to select files based on deletion statistics and rewrite them independently of the built-in small-file selection policy. ### Solution Add `FileStoreWrite::CustomizeCompact(const CompactRequest&)`, where `CompactRequest` contains partition values, a bucket, and distinct data file names. The API should submit compaction asynchronously and reuse the existing compact manager. Results and background errors should be collected through `PrepareCommit`, following the existing `Compact` lifecycle. Require `bucket-append-ordered=false`, `write-only=false`, and a dedicated writer with the full schema. ### Anything else? The initial scope is fixed-bucket append tables without real-time mode or data evolution. Callers must serialize deletion-vector updates and compaction for the same partition-bucket until commit or discard. ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
