fallintoplace commented on PR #1392: URL: https://github.com/apache/iceberg-go/pull/1392#issuecomment-4892188129
I did find some ways nil lineage can leak into compaction: - malformed/non-compliant v3 manifest lists could produce mixed tasks - future/custom remote scan planning could return tasks without FirstRowID - distributed/custom task serialization could drop FirstRowID - a stale plan made immediately after a metadata-only v2→v3 upgrade can have all-nil tasks, then a concurrent first v3 commit can assign row IDs to those same source files before the rewrite commits -- 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]
