You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@spark.apache.org by "kecheung (via GitHub)" <gi...@apache.org> on 2023/02/03 01:14:57 UTC

[GitHub] [spark] kecheung commented on pull request #39779: [SPARK-42222][SQL][3.3] Make error clearer when table not found in SupportsCatalogOptions catalog

kecheung commented on PR #39779:
URL: https://github.com/apache/spark/pull/39779#issuecomment-1414580579

   @HyukjinKwon I cannot agree that this is an "improvement" to the error message. A perfectly valid scenario is that any application previously in Spark 3.2 could handle NoSuchTableException, NoSuchDatabaseException, NoSuchNamespaceException differently.
   
   In the current code, the exception now returned is None.get and the application can no longer handle or differentiate between the 3 exceptions.


-- 
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: reviews-unsubscribe@spark.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscribe@spark.apache.org
For additional commands, e-mail: reviews-help@spark.apache.org