danzhewuju opened a new issue, #11123: URL: https://github.com/apache/paimon/issues/11123
### Search before asking - [x] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version Paimon 1.4 ### Compute Engine Flink 2.2 ### Minimal reproduce step 1. Create a primary-key table with two business columns: ```text id INT payload STRING PRIMARY KEY (id) ``` Configure: ```text changelog-producer = input table-read.sequence-number.enabled = true ``` 2. Commit an insert: ```text INSERT: (1, "before") ``` 3. In a second commit, write both records together: ```text UPDATE_BEFORE: (1, "before") UPDATE_AFTER: (1, "after") ``` 4. Read the table's `$binlog` system table using a streaming scan restored to the second commit's snapshot. 5. Consume the planned streaming split. The reader fails when copying the `UPDATE_BEFORE` record. This also happens when the output projection excludes `_SEQUENCE_NUMBER`, because the underlying reader still includes the sequence-number column. ### What doesn't meet your expectations? The streaming binlog reader should return one packed update containing the before and after values: ```text +U 1 [1,1] [before,after] ``` Instead, it throws: ```text java.lang.IllegalArgumentException: Row arity: 3, but serializer arity: 2 at org.apache.paimon.data.serializer.InternalRowSerializer.copy(...) at org.apache.paimon.reader.PackChangelogReader$InternRecordIterator.next(...) ``` Batch reads do not perform update pairing, so the existing batch tests do not exercise this failure path. Insert-only streams also avoid the update-before copy. <img width="3268" height="1170" alt="image" src="https://github.com/user-attachments/assets/2da4baa0-88ae-4599-86e7-11f1779b2b15" /> ### Anything else? _No response_ ### 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]
