[ 
https://issues.apache.org/jira/browse/PIG-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571031#action_12571031
 ] 

Pi Song commented on PIG-98:
----------------------------

Just want to share my thought here.

1. Log messages and application messages are different and should be treated 
differently. I am still not quite convinced about the way that logging 
framework is used for reporting error messages to user.

2. The interactive error messages in Grunt should be "user-friendly" shell 
level error message where in-depth details are logged using logging framework. 

3. In case the user wants to see stacktrace in Grunt, that can be optional 
(which might be considered on by default as I believe most users are developers 
rather than end-users). It can be turned on/off like the way "set debug on" 
works.

4. For embedded Pig engine, the PigException thrown from the engine should 
contain "User-friendly" error message plus the stacktrace in inner exception 
wrapped inside the PigException (Like the way SQLException works in most 
languages)


> 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.

Reply via email to