laskoviymishka commented on PR #728: URL: https://github.com/apache/iceberg-go/pull/728#issuecomment-3916780787
I think we can probably split this work and collaborate in a way that avoids overlap or conflicts. Here’s how I was thinking about sequencing row-lineage work in Go: 1. Wire the V3 snapshot producer to the row-lineage state — currently in progress in #728 (foundation, append path). 2. Enforce row-lineage invariants at the commit boundary — drafted and planned right after #728. 3. Add integration tests for sequential commits — drafted, just not published yet. 4. Extend support to overwrite/delete/rewrite paths — likely the trickiest part. 5. CLI visibility + docs — follow-up polish. From what I can see, #735 seems to focus more on broader row-lineage work (read path + more complex write paths). Maybe a reasonable approach would be: 1. Merge #728 first as the base. 2. Then rebase #735 on top of it and continue with overwrite/rewrite/delete paths and the remaining gaps. If that sounds reasonable, I’m happy to keep driving 1→3, and you (@dttung2905) could take 4 (and the other remaining pieces) once #728 lands. Open to your ideas (we can park this coordination in slack if you wish) -- 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]
