tajo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hyunsik Choi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (TAJO-458) Visit methods of LogicalPlanVisitor should take a query block as parameter
Date Mon, 30 Dec 2013 15:08:50 GMT

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

Hyunsik Choi updated TAJO-458:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

This issue received +1 in reviewboard.

committed it to master branch.

> Visit methods of LogicalPlanVisitor should take a query block as parameter
> --------------------------------------------------------------------------
>                 Key: TAJO-458
>                 URL: https://issues.apache.org/jira/browse/TAJO-458
>             Project: Tajo
>          Issue Type: Improvement
>          Components: planner/optimizer
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>             Fix For: 0.8-incubating
>         Attachments: TAJO-458.patch
> A logical plan is composed of multiple query blocks. Each logical node must belong to
one query block. A query block instance  provides lots of information. So, it is essential
information in many rewrite rules and optimizer implementations. 
> However, so far, individual rewrite rule or optimizer implementation have dealt with
query block directly. It may be error-prone and cause duplicated codes. This patch refactors
each visitor method of LogicalPlanVisitor to take a query block as a parameter.  
> I'm expecting that this change will provide more convenience for rewrite rules and optimization

This message was sent by Atlassian JIRA

View raw message