[jira] [Updated] (HIVE-14186) Display the UDF exception message in MapReduce in beeline console
[ https://issues.apache.org/jira/browse/HIVE-14186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated HIVE-14186: Resolution: Fixed Fix Version/s: 2.2.0 Status: Resolved (was: Patch Available) Pushed to master. Thanks Yongzhi for reviewing. > Display the UDF exception message in MapReduce in beeline console > -- > > Key: HIVE-14186 > URL: https://issues.apache.org/jira/browse/HIVE-14186 > Project: Hive > Issue Type: Improvement > Components: Beeline >Reporter: Aihua Xu >Assignee: Aihua Xu > Fix For: 2.2.0 > > Attachments: HIVE-14186.1.patch > > > Currently when Mapper or Reducer fails, the beeline console will print the > following error. > Error: Error while processing statement: FAILED: Execution Error, return code > 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask (state=08S01,code=2) > It would be helpful if we can print the exceptions from the mapreduce to the > beeline console directly so you don't need to dig into the MR log to find it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (HIVE-14186) Display the UDF exception message in MapReduce in beeline console
[
https://issues.apache.org/jira/browse/HIVE-14186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aihua Xu updated HIVE-14186:
Status: Patch Available (was: Open)
Patch-1: When we call the UDF and UDF throws the exception, the UDF invoke
rethrows a new exception with new message. If the --verbose=true is turned on,
actually we should be able to see the details on the client. Made the small
change in the patch-1 to add the real exception for InvocationTargetException
so the user can see the meaningful exception even without the verbose mode.
Here is result to run a UDF.
{noformat}
Error: Error while compiling statement: FAILED: SemanticException [Error
10014]: Line 1:7 Wrong arguments ''test'':
org.apache.hadoop.hive.ql.metadata.HiveException: Unable to execute method
public org.apache.hadoop.io.Text SampleUDF.evaluate(org.apache.hadoop.io.Text)
throws org.apache.hadoop.hive.ql.metadata.HiveException with arguments {test}:
Some exception from UDF (state=42000,code=10014)
{noformat}
Unfortunately I don't see a way to add a unit test.
> Display the UDF exception message in MapReduce in beeline console
> --
>
> Key: HIVE-14186
> URL: https://issues.apache.org/jira/browse/HIVE-14186
> Project: Hive
> Issue Type: Improvement
> Components: Beeline
>Reporter: Aihua Xu
>Assignee: Aihua Xu
> Attachments: HIVE-14186.1.patch
>
>
> Currently when Mapper or Reducer fails, the beeline console will print the
> following error.
> Error: Error while processing statement: FAILED: Execution Error, return code
> 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask (state=08S01,code=2)
> It would be helpful if we can print the exceptions from the mapreduce to the
> beeline console directly so you don't need to dig into the MR log to find it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (HIVE-14186) Display the UDF exception message in MapReduce in beeline console
[ https://issues.apache.org/jira/browse/HIVE-14186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aihua Xu updated HIVE-14186: Summary: Display the UDF exception message in MapReduce in beeline console (was: Display the exception message in MapReduce in beeline console ) > Display the UDF exception message in MapReduce in beeline console > -- > > Key: HIVE-14186 > URL: https://issues.apache.org/jira/browse/HIVE-14186 > Project: Hive > Issue Type: Improvement > Components: Beeline >Reporter: Aihua Xu >Assignee: Aihua Xu > Attachments: HIVE-14186.1.patch > > > Currently when Mapper or Reducer fails, the beeline console will print the > following error. > Error: Error while processing statement: FAILED: Execution Error, return code > 2 from org.apache.hadoop.hive.ql.exec.mr.MapRedTask (state=08S01,code=2) > It would be helpful if we can print the exceptions from the mapreduce to the > beeline console directly so you don't need to dig into the MR log to find it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
