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

Jihoon Son commented on TAJO-481:
---------------------------------

In this issue, I'll make a simple tree structure discussed in TAJO-483.

> 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
(v6.1.5#6160)

Reply via email to