wgtmac opened a new pull request, #17234:
URL: https://github.com/apache/iceberg/pull/17234

   ## Summary
   - Preserve `data-sequence-number` when serializing and parsing REST 
content-file JSON.
   - Add `data-sequence-number` to the REST OpenAPI `ContentFile` schema.
   - Add focused parser coverage for content files and fetch-scan-task 
responses.
   
   ## Problem
   REST scan-task payloads serialize scan task files through 
`ContentFileParser`. The payload preserved `first-row-id`, but dropped the data 
sequence number copied from the content file's manifest entry. Row-lineage 
readers need that sequence number to materialize 
`_last_updated_sequence_number` when the physical column is null or absent.
   
   ## Spec Basis
   - The format spec says that when `_last_updated_sequence_number` is null, 
readers assign the `sequence_number` of the data file's manifest entry.
   - The sequence number inheritance section defines the manifest-entry data 
sequence number that is inherited when it is not explicitly written.
   
   ## Testing
   - `JAVA_HOME=/Users/gangwu/.sdkman/candidates/java/17.0.18-zulu ./gradlew 
spotlessApply :iceberg-core:test --tests 
org.apache.iceberg.TestContentFileParser.dataFileSequenceNumber --tests 
org.apache.iceberg.rest.responses.TestFetchScanTasksResponseParser.fileScanTaskDataSequenceNumber`
   
   ---
   **AI Disclosure**
   - Model: [unknown - human to fill in]
   - Platform/Tool: OpenAI Codex
   - Human Oversight: [unknown - human to fill in]
   - Prompt Summary: Fix REST content-file data sequence number serialization 
for row lineage scan tasks.
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to