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.
