[
https://issues.apache.org/jira/browse/HIVE-1457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12888741#action_12888741
]
John Sichi commented on HIVE-1457:
----------------------------------
One from Dennis
----
On Jul 13, 2010, at 2:43 PM, Dennis DeCoste wrote:
This suddenly started happening, after I just added a couple of arrays in my
UDAF code and rebuilt the JAR ... the Hive query that had worked before
suddenly now reports the following error.
Does this NoSuchMethodException on "J.<init>" ring any bells for anyone? (I
searched the Hive mail list and didn't see any old mentions of this ....).
I.e. what is it a symptom of?
Resolution:
Nevermind .... I had accidentally added one of my newly introduced vector
declares as "long foo[];" instead of "long[] foo;" -- and it created the JAR
fine. So just a silly Java programming/typo error ...
> improve diagnostics for incorrectly written UDAF implementations
> ----------------------------------------------------------------
>
> Key: HIVE-1457
> URL: https://issues.apache.org/jira/browse/HIVE-1457
> Project: Hadoop Hive
> Issue Type: Bug
> Components: UDF
> Affects Versions: 0.6.0
> Reporter: John Sichi
> Assignee: John Sichi
> Fix For: 0.7.0
>
>
> For both reflective and generic UD(A)F, I've noticed cases where an
> incorrectly written Java class will cause UDF creation or execution to fail,
> but with poor diagnostics (e.g. NPE or non-obvious Java reflective
> exception), requiring the user to guess what the problem is by comparison
> with a working class.
> Specific examples to follow; I think I have seen the following cases:
> * incorrect accessibility on a class or method (e.g. private instead of
> public)
> * missing no-arg constructor
> * incorrect method return type
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
