nastra commented on issue #10003: URL: https://github.com/apache/iceberg/issues/10003#issuecomment-2007780751
I think the problem is actually the expectation of the `SparkSessionCatalog` behavior and that the documentation doesn't do a good job of describing what it's purpose is (I've stumbled into this as well). Most of the time you'd want to use `SparkCatalog`. The `SparkSessionCatalog` currently doesn't work well if the underlying catalog is a non-hive catalog (and you're using the JDBC catalog in your example). The namespace behavior in `SparkSessionCatalog` also has issues currently, especially if using a non-hive catalog that requires namespaces to be created before creating a table in that namespace). If you look at the implementation of `SparkSessionCatalog` around how it deals with namespaces and tables, it actually delegates to Spark's session catalog and that is most likely the underlying issue here. That being said, this issue should be updated to reflect that this is an issue with `SparkSessionCatalog` when using it with a non-Hive catalog and we should fix the behavior. -- 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
