hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shubham Chopra (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-161) Rework physical plan
Date Fri, 04 Apr 2008 14:11:24 GMT

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

Shubham Chopra updated PIG-161:
-------------------------------

    Attachment: pogenerate.patch

The new POGenerate with test cases attached.

I have tried to implement changes Alan suggested by not wrapping data in tuples and bags and
trying to have a template for the output tuple. I have used an array instead of a Tuple for
the template. I think writing to the final output tuple straight away would need some overhead
in keeping a track of the sizes of the flattened tuples. So instead I put the final values
in the array and flatten it out (wherever flattening is needed) into a tuple. There is no
creation of any intermediate databags or tuples to wrap the data.

I have also tried to explain what I am trying to do in getNext(). Pls. suggest if further
elaboration is needed.

> Rework physical plan
> --------------------
>
>                 Key: PIG-161
>                 URL: https://issues.apache.org/jira/browse/PIG-161
>             Project: Pig
>          Issue Type: Sub-task
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: arithmeticOperators.patch, incr2.patch, Phy_AbsClass.patch, pogenerate.patch,
pogenerate.patch
>
>
> This bug tracks work to rework all of the physical operators as described in http://wiki.apache.org/pig/PigTypesFunctionalSpec

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