[
https://issues.apache.org/jira/browse/SPARK-21318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Owen updated SPARK-21318:
------------------------------
Issue Type: Improvement (was: Bug)
(not a bug)
Internally, can it distinguish between something that registered and failed to
init, from something that wasn't registered? does it keep the registration in
this case? it effectively isn't available for use, right?
> 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: [email protected]
For additional commands, e-mail: [email protected]
