EgorFokin opened a new issue, #19290:
URL: https://github.com/apache/hudi/issues/19290
### Bug Description
**What happened:**
Cleaner deleted log files scheduled for compaction, resulting in compaction
failure:
java.io.FileNotFoundException: No such file or directory:
s3a://datalake/raw/hudi_table/hudi_partition/.00000001-0000-0000-0000-000000000000-0_20260624234325732.log.1_0-1-4
**What you expected:**
I see that cleaner has an explicit check that a log file shouldn't be in the
compaction request file for it to be cleaned. This should've prevented it from
deleting the file.
**Steps to reproduce:**
- Have a log file which has an instant time older than the base file
- Run compaction scheduling, it will pick up this log file
- Run cleaner, it will delete this log file
- Run compaction execution, it will fail
### Environment
**Hudi version:** 1.0.2
**Query engine:** (Spark/Flink/Trino etc): Flink writer, Spark table services
**Relevant configs:**
```
"--hoodie-conf", "hoodie.datasource.write.recordkey.field={{
params.table_record_key_fields }}",
"--hoodie-conf", "hoodie.bucket.index.hash.field={{
params.table_record_key_fields }}",
"--hoodie-conf", "hoodie.table.type=MERGE_ON_READ",
"--hoodie-conf", "hoodie.write.status.storage.level=MEMORY_AND_DISK_SER",
"--hoodie-conf",
"hoodie.write.concurrency.mode=NON_BLOCKING_CONCURRENCY_CONTROL",
"--hoodie-conf",
"hoodie.write.lock.provider=org.apache.hudi.aws.transaction.lock.DynamoDBBasedLockProvider",
"--hoodie-conf", "hoodie.write.lock.dynamodb.table={{ params.dynamodb_table
}}",
"--hoodie-conf", "hoodie.write.lock.dynamodb.partition_key={{
params.table_name }}",
"--hoodie-conf", "hoodie.index.type=BUCKET",
"--hoodie-conf", "hoodie.metadata.enable=false",
"--hoodie-conf", "hoodie.index.bucket.engine=SIMPLE",
"--hoodie-conf", "hoodie.bucket.index.num.buckets=4"
```
### Logs and Stack Trace
_No response_
--
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]
