You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2013/12/28 18:31:50 UTC
[jira] [Commented] (TAJO-458) Visit methods of LogicalPlanVisitor
should take a query block as parameter
[ https://issues.apache.org/jira/browse/TAJO-458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13858073#comment-13858073 ]
Hyunsik Choi commented on TAJO-458:
-----------------------------------
I just submitted the patch to the reviewboard.
https://reviews.apache.org/r/16495
> 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
>
>
> 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 development.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)