tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jihoon Son (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TAJO-481) Logical plan refactoring
Date Tue, 07 Jan 2014 09:29:51 GMT

    [ https://issues.apache.org/jira/browse/TAJO-481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13864035#comment-13864035

Jihoon Son edited comment on TAJO-481 at 1/7/14 9:28 AM:

Welcome any suggestions to improve the logical plan, including the naming.

was (Author: jihoonson):
Welcome to any suggestions to improve the logical plan, including the naming.

> Logical plan refactoring
> ------------------------
>                 Key: TAJO-481
>                 URL: https://issues.apache.org/jira/browse/TAJO-481
>             Project: Tajo
>          Issue Type: Improvement
>          Components: distributed query plan, planner/optimizer
>    Affects Versions: 0.8-incubating
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
> The current logical plan has some problems such as requiring a complex logic to make
a master plan, hard to be extended to support multiple outputs, and inefficient de/serialization.

> In this issue, we improve the logical plan to handle these problems. We should reflect
the followings.
> * Change the logical plan from tree to DAG to easily support multiple outputs
> * Enable to connect logical nodes and data channels
> ** This makes GlobalPlanner simpler, since it removes complex codes for scan node creation.
> ** Data channel has two types of materialized data channel and stream data channel (for
the future). The materialized data channel should contain the store information for sender
and the scan information for receiver.
> * Refactor the de/serialization of logical plan 
> * Add a compare tool and hash tool for logical nodes
> ** During the query planning, logical nodes are compared and hashed in various ways.
To support various comparison and hashing, we need a new class such as LogicalNodeComparator
and LogicalNodeHashCoder

This message was sent by Atlassian JIRA

View raw message