[
https://issues.apache.org/jira/browse/PIG-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12894320#action_12894320
]
Ashutosh Chauhan commented on PIG-1531:
---------------------------------------
This is because in InputOutputFileVisitor#visit() Pig defines its own
{{errMsg}} String and uses that to throw PlanValidationException. It should use
the error String of the Exception it has caught.
I have not checked at other places. But I have a hunch that it happens at few
other places in Pig as well. This is a real usability issue since generic
message is usually useless and Pig misses an opportunity to provide an useful
bit of information in error scenarios. From that point on, user has to go open
the log file and scroll among tens of lines of stack trace and only if she is
familiar with Pig will spot that error String.
> Pig gobbles up error messages
> -----------------------------
>
> Key: PIG-1531
> URL: https://issues.apache.org/jira/browse/PIG-1531
> Project: Pig
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Ashutosh Chauhan
> Fix For: 0.8.0
>
>
> Consider the following. I have my own Storer implementing StoreFunc and I am
> throwing FrontEndException (and other Exceptions derived from PigException)
> in its various methods. I expect those error messages to be shown in error
> scenarios. Instead Pig gobbles up my error messages and shows its own generic
> error message like:
> {code}
> 010-07-31 14:14:25,414 [main] ERROR org.apache.pig.tools.grunt.Grunt - ERROR
> 2116: Unexpected error. Could not validate the output specification for:
> default.partitoned
> Details at logfile: /Users/ashutosh/workspace/pig/pig_1280610650690.log
> {code}
> Instead I expect it to display my error messages which it stores away in that
> log file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
