hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pi Song (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-158) Rework logical plan
Date Thu, 03 Apr 2008 13:02:24 GMT

    [ https://issues.apache.org/jira/browse/PIG-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585095#action_12585095

Pi Song commented on PIG-158:

The complexity will come from the fact that we change a flat computation to a recursive one.
Naturally if we change the way we model from flat data flow to nested data flow, this is just
unavoidable. In most cases where the main state doesn't care about sub-states (ex. peephole
optimization), this just adds a bit more boilerplate code (no brain). On the other hand, for
a logic like type-checking, we will need to do a bit more work but I think there aren't so
many like it.

BTW, I think this new model is more logical and more understandable than having operators
at different levels floating around in the same plan. This should in fact help keep the whole
complexity (due to ambiguity) down.

> Rework logical plan
> -------------------
>                 Key: PIG-158
>                 URL: https://issues.apache.org/jira/browse/PIG-158
>             Project: Pig
>          Issue Type: Sub-task
>          Components: impl
>            Reporter: Alan Gates
>            Assignee: Alan Gates
>         Attachments: logical_operators.patch, logical_operators_rev_1.patch, logical_operators_rev_2.patch,
> Rework the logical plan in line with http://wiki.apache.org/pig/PigExecutionModel

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

View raw message