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

   ## Search before asking
   
   - [x] I searched the existing issues and found no duplicate request.
   
   ## Motivation
   
   We encountered this problem while investigating commit conflicts in a 
customer's production environment. The `Base entries` and `Changes` lists show 
file names and buckets, but print partitions as opaque `BinaryRow@...` values. 
This makes it difficult to identify the affected partitions and slows down 
troubleshooting.
   
   A similar example appears in [batch compaction report 
#6955](https://github.com/apache/paimon/issues/6955). Data Evolution row-range 
conflict messages have the same problem for data files and dedicated 
blob/vector files.
   
   ## Solution
   
   Use the table's existing partition path formatter to make these entries 
readable. For example:
   
   ```text
   Before:
   {kind=DELETE, partition=org.apache.paimon.data.BinaryRow@..., bucket=2, 
fileName=data-old.parquet, ...}
   
   After:
   {kind=DELETE, partition=dt=2026-01-05/hr=12/, bucket=2, 
fileName=data-old.parquet, ...}
   ```
   
   Apply this to:
   
   - Full and summarized `Base entries` / `Changes` lists.
   - Data-file and dedicated-file entries in Data Evolution row-range conflict 
messages.
   
   Preserve other entry fields, deletion-vector metadata, the existing summary 
limit, exception types, and original cause. Use an explicit value for 
non-partitioned tables and retain the original entry output if partition 
formatting fails.
   
   ## Anything else?
   
   This improves diagnostics only; it does not change conflict detection, 
commit behavior, or retries. Issue #6955 illustrates the readability problem, 
but fixing its underlying compaction failure is outside this request's scope.
   
   ## 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]

Reply via email to