brunomendola commented on issue #12223: URL: https://github.com/apache/iceberg/issues/12223#issuecomment-2665131061
@singhpk234 I think you're right. The fact is that I came here after I found the issue in the Python repo. The PyIceberg documentation doesn't explain the transaction feature as well as the Java API documentation (https://iceberg.apache.org/docs/1.5.0/api/#update-operations)... the need for a wrapping transaction can be inferred from there. Maybe it's worth adding a note to the "Update operations" section of the documentation, indicating clearly that you won't see the uncommitted changes when doing subsequent update operations, and if you need such kind of schema operations and also need atomicity, you should use transacions. -- 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
