emkornfield commented on PR #11039: URL: https://github.com/apache/iceberg/pull/11039#issuecomment-2623021449
> > @hesham-medhat @rdblue - could you pls give an update on this PR? It seems it would massively simplify the Iceberg table management in GCP for non-spark usecases. > > thanks! > > Just a curious question - Currently how are you supporting non-spark usecases at all? scheduling a metadata copy in iceberg metadata format, and then pointing other engines to that from that? However, even with this PR merge, the non spark usecases must have integrations with BigQuery metastore for the simplification to happen right? what am I missing @vrishin-bolt This change should support anything using Iceberg's Catalog interface. So Spark, Beam and Flink I believe should be able to use it. Trino uses its own interface and there is an [open issue](https://github.com/trinodb/trino/issues/20031) to support BQMS. For non-JVM systems you are correct, those are not supported initially and GCP will need to work either contribute/collaborate on other clients. If there are critical use-cases for BQMS that you would like to see covered please contact BQ (I think you might have done so already). -- 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
