You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Aleksandar Tomic (Jira)" <ji...@apache.org> on 2023/11/29 15:39:00 UTC

[jira] [Commented] (SPARK-46036) raise_error should only take the error class parameter for internal usage

    [ https://issues.apache.org/jira/browse/SPARK-46036?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791143#comment-17791143 ] 

Aleksandar Tomic commented on SPARK-46036:
------------------------------------------

This is done now.

> raise_error should only take the error class parameter for internal usage
> -------------------------------------------------------------------------
>
>                 Key: SPARK-46036
>                 URL: https://issues.apache.org/jira/browse/SPARK-46036
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 4.0.0
>            Reporter: Wenchen Fan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.0.0
>
>
> In [https://github.com/apache/spark/pull/42985] , we extended the `raise_error` function to take an extra error-class parameter. However, this is too powerful as users may use it to throw special internal errors that we don't expect them to throw.
> It's useful to have this `raise_error` extension for internal usage. We should create an `ExpressionBuilder` for `raise_error` function, so that we only allow end users to pass the error message, not error class.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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