Re: [PR] [SPARK-43255][SQL]Replace the error class _LEGACY_ERROR_TEMP_2020 by an internal error [spark]

["eejbyfeldt (via GitHub)" <gi...@apache.org>]

eejbyfeldt commented on PR #45302:
URL: https://github.com/apache/spark/pull/45302#issuecomment-1972662822

   @MaxGekk To me it seems correct to make it an internal error. I think the cases it could come up from using user defined types in the Scala API are meant to be captured earlier by other code and it failing with this would indicate a spark bug.
   
   >  If I am not wrong: StaticInvoke could trigger this error and StaticInvoke could be used by a user?
   
   > I saw in the past users use StaticInvoke in their library.
   
   My understanding is that classes `org.apache.spark.sql.catalyst` were consider semi private/developer api.  But I have not really found the documentation where this is clarified so maybe I have misunderstood something. Anyway to me it does not seem realistic to provide good errors for all possible missuses of classes that live in there.


-- 
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