Re: [I] [bug] Cannot perform table scan on V1 table [iceberg-python]

kevinjqliu commented on issue #1194: URL: https://github.com/apache/iceberg-python/issues/1194#issuecomment-2571387324 Spark's V1 manifest list writer contains the optional `added_rows_count` field. https://github.com/apache/iceberg/blob/fcd5dd932a21066d6127c94c50f3de43e8c2d80c/cor

Re: [I] [bug] Cannot perform table scan on V1 table [iceberg-python]

kevinjqliu commented on issue #1194: URL: https://github.com/apache/iceberg-python/issues/1194#issuecomment-2571385510 #1484 is a better, isolated test. It's using the minimal required schema for a v1 table manifest list -- This is an automated message from the Apache Git Service. To res

Re: [I] [bug] Cannot perform table scan on V1 table [iceberg-python]

kevinjqliu commented on issue #1194: URL: https://github.com/apache/iceberg-python/issues/1194#issuecomment-2570622923 Added a reproducible test in #1483, i had to save the biglake iceberg table locally. please take a look -- This is an automated message from the Apache Git Service. To r

Re: [I] [bug] Cannot perform table scan on V1 table [iceberg-python]

Fokko commented on issue #1194: URL: https://github.com/apache/iceberg-python/issues/1194#issuecomment-2445957746 @kevinjqliu Thanks for raising this. Can you elaborate on what you encountered when reading a V1 table? The Iceberg metadata is forward compatible, meaning we can turn any V1 t