spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "StanZhai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SPARK-21318) The exception message thrown by `lookupFunction` is ambiguous.
Date Wed, 05 Jul 2017 14:19:00 GMT

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

StanZhai commented on SPARK-21318:
----------------------------------

yes.
It has been registered into the `functionRegistry`, but it's not available for use.

> The exception message thrown by `lookupFunction` is ambiguous.
> --------------------------------------------------------------
>
>                 Key: SPARK-21318
>                 URL: https://issues.apache.org/jira/browse/SPARK-21318
>             Project: Spark
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 2.0.0, 2.0.1, 2.0.2, 2.1.0, 2.1.1
>            Reporter: StanZhai
>            Priority: Minor
>
> The function actually exists in current selected database, but the exception message
is: 
> {code}
> This function is neither a registered temporary function nor a permanent function registered
in the database 'default'.
> {code}
> My UDF has already been registered in the current database. But it's failed to init during
lookupFunction. 
> The exception message should be:
> {code}
> No handler for Hive UDF 'site.stanzhai.UDAFXXX': org.apache.hadoop.hive.ql.exec.UDFArgumentLengthException:
Two arguments is expected
> {code}
> This is not conducive to positioning problems.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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


Mime
View raw message