tanmayrauth opened a new pull request, #1043:
URL: https://github.com/apache/iceberg-go/pull/1043

     After investigating the codebase, I found that the write-side row lineage 
is already fully implemented on main:                                           
                                                                      
                                                                                
                                                                                
                                                                     
     - Manifest-list writer assigns first_row_id to data manifests 
(manifest.go:1508)                                                              
                                                                                
  
     - OCC retry re-derives first_row_id from fresh metadata 
(snapshot_producers.go:1029)
     - validateAndUpdateRowLineage advances next-row-id at commit time 
(metadata.go:507)                                                               
                                                                              
     - Scanner synthesizes _row_id at read time (arrow_scanner.go:425)    
     
     All I added was two tests that prove the existing code works correctly 
under the specific scenarios:                                                   
                                                     
     1. Fast-append + OCC retry → first_row_id rebases correctly
     2. Merge-append + OCC retry → merged manifests get correct first_row_id 
from list writer     
     
   
   
   Closes: #998


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