[
https://issues.apache.org/jira/browse/SPARK-33240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17220514#comment-17220514
]
Apache Spark commented on SPARK-33240:
--------------------------------------
User 'HeartSaVioR' has created a pull request for this issue:
https://github.com/apache/spark/pull/30147
> Fail fast when fails to instantiate configured v2 session catalog
> -----------------------------------------------------------------
>
> Key: SPARK-33240
> URL: https://issues.apache.org/jira/browse/SPARK-33240
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 3.0.0, 3.0.1, 3.1.0
> Reporter: Jungtaek Lim
> Priority: Major
>
> Now Spark fails back to use "default catalog" when Spark fails to instantiate
> configured v2 session catalog.
> While the error log message says nothing about why the instantiation has been
> failing and the error log message pollutes the log file (as it's logged every
> time when resolving the catalog), it should be considered as "incorrect"
> behavior as end users are intended to set the custom catalog and Spark
> sometimes ignores it, which is against the intention.
> We should simply fail in the case so that end users indicate the failure
> earlier and try to fix the issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
