Re: [I] Newly created table does not detect commit failures [iceberg-python]

kevinjqliu commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2755132643 this was fixed by nessie https://github.com/projectnessie/nessie/issues/10062 -- This is an automated message from the Apache Git Service. To respond to the message,

Re: [I] Newly created table does not detect commit failures [iceberg-python]

kevinjqliu closed issue #1366: Newly created table does not detect commit failures URL: https://github.com/apache/iceberg-python/issues/1366 -- 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 speci

Re: [I] Newly created table does not detect commit failures [iceberg-python]

HaraldVanWoerkom commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2503234175 Hi @Fokko , Thanks for taking the time to look into this. If I understand correctly, in the case of an empty table, you send an update request to the ca

Re: [I] Newly created table does not detect commit failures [iceberg-python]

Fokko commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2501843565 Here's the logic: https://github.com/apache/iceberg-python/blob/1e9bdc21d95d2702f0777b21c61409262d1e3052/pyiceberg/table/update/snapshot.py#L271-L279 We always set

Re: [I] Newly created table does not detect commit failures [iceberg-python]

Fokko commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2501830533 As a side note, we don't have a proper retry strategy in Iceberg yet. To appends should not cause a conflict right away because they don't interfere. Instead what should happen

Re: [I] Newly created table does not detect commit failures [iceberg-python]

kevinjqliu commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2501614001 @HaraldVanWoerkom if you have a reproducible process, can you check if this occurs with another catalog? For example, this one that we use for integration tests https:

Re: [I] Newly created table does not detect commit failures [iceberg-python]

HaraldVanWoerkom commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2500804105 Hi @Fokko, I verified with 0.8.0, the problem is still there. -- This is an automated message from the Apache Git Service. To respond to the message, please log

Re: [I] Newly created table does not detect commit failures [iceberg-python]

HaraldVanWoerkom commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2498218809 Hi @Fokko, We are using Nessie 0.99.0. I have not tried 0.8.0 yet, I'll try that. I get the impression that we are talking about different things. I c

Re: [I] Newly created table does not detect commit failures [iceberg-python]

Fokko commented on issue #1366: URL: https://github.com/apache/iceberg-python/issues/1366#issuecomment-2498141453 Hey @HaraldVanWoerkom thanks for reaching out here. Two questions: - Which catalog are you using? - Have you tried updating to 0.8.0 to ensure that the issue persists?

[I] Newly created table does not detect commit failures [iceberg-python]

HaraldVanWoerkom opened a new issue, #1366: URL: https://github.com/apache/iceberg-python/issues/1366 ### Apache Iceberg version 0.7.1 ### Please describe the bug 🐞 I have multiple processes that write to a table. They sometimes clash, resulting in a failed commit, which