hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alan Gates (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-159) Make changes to the parser to support new types functionality
Date Thu, 05 Jun 2008 15:11:45 GMT

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

Alan Gates commented on PIG-159:
--------------------------------

When you say "move the schema parsing to a different lexical state" do you mean pull it out
of the parser and do it after parsing?  In general I agree that we should do that.  But can
we hold off for a bit?  We just got our end to end tests starting to run.  I'd like to not
do any major refactoring at the moment.

As far as allowing keywords as aliases, we really need to disallow that altogether.  Let's
not go to any extra effort to make sure users can name a field group in a schema definition.

> Make changes to the parser to support new types functionality
> -------------------------------------------------------------
>
>                 Key: PIG-159
>                 URL: https://issues.apache.org/jira/browse/PIG-159
>             Project: Pig
>          Issue Type: Sub-task
>          Components: impl
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: parser_chages_v10.patch, parser_chages_v11.patch, parser_chages_v12.patch,
parser_chages_v13.patch, parser_chages_v5.patch, parser_chages_v6.patch, parser_chages_v7.patch,
parser_chages_v8.patch, parser_chages_v9.patch
>
>
> In order to support the new types functionality described in http://wiki.apache.org/pig/PigTypesFunctionalSpec,
the parse needs to change in the following ways:
> 1) AS needs to support types in addition to aliases.  So where previously it was legal
to say:
> a = load 'myfile' as a, b, c;
> it will now also be legal to say
> a = load 'myfile' as a integer, b float, c chararray;
> 2) Non string constants need to be supported.  This includes non-string atomic types
(integer, long, float, double) and the non-atomic types bags, tuples, and maps.
> 3) A cast operator needs to be added so that fields can be explicitly casted.
> 4) Changes to DEFINE, to allow users to declare arguments and return types for UDFs

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message