Eduard Tudenhoefner
Eduard Tudenhoefner
Yep, it was due to disk space. So maybe something in Iceberg Spark 3.3 has a memory leak and that's how it surfaces
@N-o-Z can you elaborate please what exactly you're trying to achieve? Are you trying to implement multi-table commits on the server? For `COMMIT_TRANSACTION` the approach is very simplistic and does...
> I plan to resolve https://github.com/apache/iceberg/issues/7162 by adding vectorized readers for all v2 encodings. This is the 1st patch. @wgtmac do you by any chance have all other changes that...
hey @wgtmac sorry for the long wait here but I don't have any spare cycles atm to review this.
@amogh-jahagirdar or @RussellSpitzer can you guys also take a look at this please?
the only thing I'm a little concerned about is the `CachingCatalog`, since it uses only the `TableIdentifier` as the cache key and doesn't consider the snapshot id of a table....
> Do these need to be addressed in this PR? > > ``` > TestSpark3Util > testDescribeSortOrder FAILED > org.junit.ComparisonFailure: Sort order isn't correct. expected: but was: > at org.junit.Assert.assertEquals(Assert.java:117)...
@epgif can you please address the test failures?
@jacobmarble sorry for the delay here. I'm traveling this week and should be able to get to this PR after the Iceberg summit
@jacobmarble I'll try to do another round this week once merge conflicts have been resolved. Also I think it would be good to get a review from @rdblue on this...