HeartSaVioR edited a comment on issue #1144:
URL: https://github.com/apache/iceberg/issues/1144#issuecomment-663370540
I've also encountered this issue, and found the reason - Spark's default
catalog still has same limitation in different code path, so if users decide to
override default Spark catalog with Iceberg, the limitation still comes out.
```
org.apache.spark.sql.AnalysisException: The namespace in session catalog
must have exactly one name part: spark_catalog.default.table1.files;
at
org.apache.spark.sql.connector.catalog.LookupCatalog$SessionCatalogAndIdentifier$.unapply(LookupCatalog.scala:65)
at
org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$.org$apache$spark$sql$catalyst$analysis$Analyzer$ResolveRelations$$lookupRelation(Analyzer.scala:1009)
at
org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$$anonfun$apply$9.applyOrElse(Analyzer.scala:977)
at
org.apache.spark.sql.catalyst.analysis.Analyzer$ResolveRelations$$anonfun$apply$9.applyOrElse(Analyzer.scala:962)
at
org.apache.spark.sql.catalyst.plans.logical.AnalysisHelper.$anonfun$resolveOperatorsUp$3(AnalysisHelper.scala:90)
at
org.apache.spark.sql.catalyst.trees.CurrentOrigin$.withOrigin(TreeNode.scala:72)
...
```
(The code path is still in master branch of Spark.)
Using custom catalog would work, like `iceberg_catalog`.
I'm not sure whether it's expect or not - in other words, may need to decide
whether it is a doc issue in Iceberg or a bug in Spark. @rdblue Would you mind
if I ask your voice on this?
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
