[Bug] Dedicated Compaction for write-only table cann't clean up small files after running for a long time
- Dominant language
- Java
- Stars
- 3.4k
- Forks
- 1.4k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 396
Description
### Search before asking
- [X] I searched in the [issues](https://github.com/apache/incubator-paimon/issues) and found nothing similar.
### Paimon version
0.6
### Compute Engine
flink 1.16
### Minimal reproduce step
1. start a flink job for writing to paimon table with mode "write-only" with checkpoint as 5s
2. start a Dedicated Compaction flink to to compact paimon table
3. after running over 1 days
4. I found some small files yesterday still exist
### What doesn't meet your expectations?
When writing and compact job runs for more than 2 days, I found small files with timestamp as "2023-12-28 19:43:36" still exist in 2023-12-29。

### Anything else?
_No response_
### Are you willing to submit a PR?
- [ ] I'm willing to submit a PR!
Contributor guide
No contributing guide indexed for this repository
Research direction
No file or test is named. Reproduce with a Paimon write-only table, Flink 1.16, 5-second checkpoints, and a dedicated compaction job running for more than two days; then trace why small files from the previous day remain. Done means the compaction job cleans up the reported old small files under this workload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100