You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/04/24 17:15:00 UTC
[jira] [Commented] (SPARK-38692) Use error classes in the compilation errors of function args
[ https://issues.apache.org/jira/browse/SPARK-38692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17527219#comment-17527219 ]
Apache Spark commented on SPARK-38692:
--------------------------------------
User 'lvshaokang' has created a pull request for this issue:
https://github.com/apache/spark/pull/36336
> Use error classes in the compilation errors of function args
> ------------------------------------------------------------
>
> Key: SPARK-38692
> URL: https://issues.apache.org/jira/browse/SPARK-38692
> Project: Spark
> Issue Type: Sub-task
> Components: SQL
> Affects Versions: 3.4.0
> Reporter: Max Gekk
> Priority: Major
>
> Migrate the following errors in QueryCompilationErrors:
> * invalidFunctionArgumentsError
> * invalidFunctionArgumentNumberError
> * functionAcceptsOnlyOneArgumentError
> * secondArgumentNotDoubleLiteralError
> * functionCannotProcessInputError
> * v2FunctionInvalidInputTypeLengthError
> * secondArgumentInFunctionIsNotBooleanLiteralError
> onto use error classes. Throw an implementation of SparkThrowable. Also write a test per every error in QueryCompilationErrorsSuite.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org