hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antonio Magnaghi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (PIG-73) Re-Design of Logical Plan
Date Wed, 23 Jan 2008 23:54:35 GMT

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

Antonio Magnaghi updated PIG-73:

    Attachment: diff.2008.01.23

- Attaching a patch with a first attempt to rewrite Logical Operators (set of operators is
not complete).

- Operator represenation using a key (scope plus ID) conforms to what is currently done in
the path for the Abstraction Layer (PIG-32)

- Operators with prefix LO represent concrete classes. Other logical operators are instead
abstract classes.

- The patch is against the branch "types" 

- I have a general question about the types:  
    public static final int FIXED = 1;
    public static final int MONOTONE = 2;
    public static final int UPDATABLE = 3;      // Reserved for future use
    public static final int AMENDABLE = 4;

For instance, UPDATABLE, I believe, is something not currently supported (comes from incremental
How about the other types above?

> Re-Design of Logical Plan
> -------------------------
>                 Key: PIG-73
>                 URL: https://issues.apache.org/jira/browse/PIG-73
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>            Reporter: Antonio Magnaghi
>            Assignee: Antonio Magnaghi
>         Attachments: diff.2008.01.23
> I am opening this new bug to track a specific work item within the broader context of
improving Pig support for optimizations.
> See related items:
>    - PIG-50 in the jira
>    - the design spec at: http://wiki.apache.org/pig/PigExecutionModel
> In particular we want to remove from the logical plan those aspects that directly relate
to the *execution* stage of a plan, hence improving decoupling. Currently EvalSpecs and Conds
(and relative pipes) are tightly coupled with logical operators.

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

View raw message