[
https://issues.apache.org/jira/browse/PIG-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571077#action_12571077
]
Alan Gates commented on PIG-98:
-------------------------------
The issue here isn't syntactic, it's semantic. Grammatically the query given is
valid. The issue is that pig doesn't currently have types beyond string, so we
force the user to tell us what type a constant is by choosing == or eq. The
parser has no way to determine whether the user chose correctly, since it
doesn't have a type system.
With the work on types being done in the type branch, these issues will be
resolved. The perlish ==/eq split will go away (though eq will still be
supported for backward compatibility) and numeric constants will be recognized
(e.g. a = filter b where $1 > 5 instead of where $1 > '5') and comparison
operators such as == will be valid for strings (so the above query should work
then).
It will be a couple of months before we have this working.
> 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.
