ZENOTME commented on issue #1104: URL: https://github.com/apache/iceberg-rust/issues/1104#issuecomment-2742230817
> For metadata conflict detection, what is the exact design outline that you are looking to implement? conflict detection implementation based on the validation phase. I would like to introduce the validation phase at SnapshotProduce apply(). After introducing it, we can have some specific implementation of kinds of validation. > For the row level detection I can start the implementation the manifest filter manager and manifest merge manager to build towards the merging snapshot producer used in the RowDelta. This can probably be done after delete files are fully implemented Thanks @jonathanc-n! - For manifest merge manager, I think it has been cover in #902. - For manifest filter manager, maybe we need it. One interesting finding is that pyiceberg don't have the manifest filter manager. In this abstraction, [it filter the delete entry directly](https://github.com/apache/iceberg-python/blob/c06e32034fbd32d5aab9b2ef19ad2d253141479d/pyiceberg/table/update/snapshot.py#L542). I haven't dive into the manifest filter manager, is needed in the future? cc @Fokko @kevinjqliu -- 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: issues-unsubscr...@iceberg.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org For additional commands, e-mail: issues-h...@iceberg.apache.org
