taoran92 opened a new issue, #1355:
URL: https://github.com/apache/paimon-rust/issues/1355

   ## Search before asking
   
   - [x] I searched in the 
[issues](https://github.com/apache/paimon-rust/issues) and found nothing 
similar.
   
   ## Motivation
   
   When a file deletion commit conflicts because another operation has already 
removed the file, the error reports the file name and bucket but omits the 
partition. This makes the affected partition harder to identify when 
troubleshooting partitioned tables.
   
   For example, a conflict in partition `dt=2026-11-09`, bucket `0`, produces:
   
   ```text
   Delete conflict: file 'data-<uuid>-0.parquet' in bucket 0 does not exist in 
the current snapshot.
   ```
   
   The error should also include readable partition values, for example 
`(partition=dt=2026-11-09, bucket=0)`. The stale deletion should continue to be 
rejected.
   
   ## Anything else?
   
   Minimal reproduction on `main` at `75a2dfc58c930f13e46410a4cf7b2c7eaca8f415`:
   
   1. Create an append-only table partitioned by the string column `dt`.
   2. Write and commit a row with `dt=2026-11-09`.
   3. Build a deletion `CommitMessage` using the committed file's partition and 
bucket, with that file in `deleted_files` and an empty `new_files` list.
   4. Create two committers with different commit users. Submit the deletion 
through the first committer, then submit a clone of the same message through 
the second.
   
   The first deletion succeeds. The second is correctly rejected with the error 
above, but the message does not identify `dt=2026-11-09`.
   
   Related: 
[apache/paimon#10565](https://github.com/apache/paimon/issues/10565) and 
[apache/paimon#10809](https://github.com/apache/paimon/issues/10809).
   
   ## Willingness to contribute
   
   - [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]

Reply via email to