Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

arul-cc commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2999388947 > [@arul-cc](https://github.com/arul-cc) btw the fix is to set `CATALOG_CLIENTS=1` for `iceberg-rest-fixture`, similar to how `CATALOG_URI` is set via env. > > can you

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

kevinjqliu commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2996773841 @arul-cc btw the fix is to set `CATALOG_CLIENTS=1` for `iceberg-rest-fixture`, similar to how `CATALOG_URI` is set via env. can you give it a try and see if this is

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

kevinjqliu commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2994389057 ok the issue is with the apache/iceberg-rest-fixture. i'll open an issue on the java side -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

kevinjqliu commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2994406941 https://github.com/apache/iceberg/issues/13366 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

kevinjqliu commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2994359501 > Caused by: org.sqlite.SQLiteException: [SQLITE_ERROR] SQL error or missing database (no such table: iceberg_tables) thats interesting. And you're using `apache/ice

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

arul-cc commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2989759477 > > Subsequent operations fail with CommitFailedException (expected due to ACID constraints) > > With more parallel calls, the table becomes inaccessible with "table not f

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

arul-cc commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2989751909 > > Suggestions for safe parallel upsert patterns in Iceberg > > maybe a good approach is to start a transaction, and only commit and the very end after all the upsert

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

kevinjqliu commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2988393517 >Suggestions for safe parallel upsert patterns in Iceberg maybe a good approach is to start a transaction, and only commit and the very end after all the upsert call

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

kevinjqliu commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2988385697 > Subsequent operations fail with CommitFailedException (expected due to ACID constraints) With more parallel calls, the table becomes inaccessible with "table not foun

Re: [I] Table metadata corruption during parallel upsert operations [iceberg-python]

jayceslesar commented on issue #2120: URL: https://github.com/apache/iceberg-python/issues/2120#issuecomment-2988014446 I dont think optimistic concurrency support is fully implemented yet https://github.com/apache/iceberg-python/issues/819 -- This is an automated message from the Apache

[I] Table metadata corruption during parallel upsert operations [iceberg-python]

arul-cc opened a new issue, #2120: URL: https://github.com/apache/iceberg-python/issues/2120 ### Apache Iceberg version 0.9.1 (latest release) ### Please describe the bug 🐞 ## Problem Description While performing parallel upsert operations on an Iceberg table, the tabl