[
https://issues.apache.org/jira/browse/PIG-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12570518#action_12570518
]
Alan Gates commented on PIG-98:
-------------------------------
I agree with you that much of our error reporting is horrible. However, we are
trying to get hadoop specific stuff out of the front end of pig. So we don't
want to use hadoop's stringifyException function in grunt. So we'll need to
lookfor for another way to mitigate this short term before we solve it long
term.
> grunt should show full exception stack
> --------------------------------------
>
> Key: PIG-98
> URL: https://issues.apache.org/jira/browse/PIG-98
> Project: Pig
> Issue Type: Improvement
> Components: grunt
> Reporter: Stefan Groschupf
> Priority: Minor
> Fix For: 0.1.0
>
> Attachments: showStackTrace-20080207.patch
>
>
> I suggest grunt should be more helpful with user errors. I just did one (a
> stupid one) and it took my too long to figure out the problem, since grunts
> error message was just not giving me a good hint:
> grunt> A = LOAD '/pigtestData.tsv' USING PigStorage(',') AS (user,age,cat);
> grunt> B = FILTER A BY cat == 'book';
> grunt> dump B;
> For input string: "book"
> Experts will see that I tried to use == instead of eq, however especially new
> users could get a little confused.
> I see two chances add Error Number and descriptive texts (Oracle style) -
> this quite a lot of work, or for now I suggest to simply dump the full
> exception text.
> At least for this early stage it would developers and users to find problems
> faster.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
