hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Santhosh Srinivasan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-159) Make changes to the parser to support new types functionality
Date Tue, 20 May 2008 19:37:55 GMT

     [ https://issues.apache.org/jira/browse/PIG-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Santhosh Srinivasan updated PIG-159:
------------------------------------

    Attachment: parser_chages_v10.patch

Patch parser_changes_v10.patch addresses:

1. Traversing LOCross inputs in the correct order
2. Changes the keyword integer to int
3. Fixes a bug in the LOUnion getSchema() method when the input schemas are null
4. Changes the LOSplit and LOSplitOutput operators in the following manner:
     - LOSplit will now maintain a list of outputs
     - LOSplitOutput will contain an inner plan for the condition on which the input is split
     - This change aids the Logical to Physical translation which has a dummy POSplit operator
and POFilter as the split outputs
     - The TypeCheckingVisitor and test/TypeCheckingValidator use the new methods for constructing
the LOSplit and LOSplitOutput operators 

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