phillipleblanc commented on PR #1087: URL: https://github.com/apache/iceberg-rust/pull/1087#issuecomment-2732962124
Thanks all for helping out here! I have a little more context on how this table came to be, but I unfortunately don't know the full history. I have an AWS Glue account with a lot of Iceberg tables that were created with AWS Glue ETL jobs that used Spark. I'm guessing at some point in the past, Spark (or the version of Spark that Glue used) had a bug where it didn't write out the V1 metadata as rigorously as it should have - and so now I have a bunch of tables that are missing the the `schema` and `partition_spec` fields. As noted in the devlist discussion, Java is able to read these tables - because Java isn't strictly following the spec. If we created a non-default feature flag called `v1-compat` (or similar) and only allowed clients that enabled that flag to be able to read these 'invalid' tables - would that be acceptable? Or perhaps some parameter that the client could set that would allow it to work? -- 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
