zeitdasein opened a new issue, #16792: URL: https://github.com/apache/iceberg/issues/16792
### Query engine Spark 3.5.0 iceberg-spark-runtime 1.4.3 ### Question Hi! I sometimes get CatalogNotFoundException: default_iceberg even though the only catalog I configure and use is my own custom one (spark.sql.catalog.my_catalog=org.apache.iceberg.spark.SparkCatalog, plus spark.sql.defaultCatalog=my_catalog), and the string default_iceberg does not appear anywhere in my configs or code. Registering default_iceberg as a second catalog in the config is not an option for me: with two catalog instances some operations resolve through one name and some through the other, and since each catalog has its own table cache, reads after writes intermittently see a stale snapshot. Is there a way to disable the implicit default_iceberg catalog entirely, or is the recommended approach to always use fully qualified identifiers (my_catalog.db.table) for every read, write, and DML so that default_iceberg is never resolved? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
