drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinfeng Ni (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DRILL-580) Drill logical or physical rules should not specify child operand
Date Tue, 06 May 2014 19:31:17 GMT

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

Jinfeng Ni updated DRILL-580:

    Attachment: DRILL-580.2.patch

Rebase on the latest master. Run a clean build against testcase suite. 

> Drill logical or physical rules should not specify child operand
> ----------------------------------------------------------------
>                 Key: DRILL-580
>                 URL: https://issues.apache.org/jira/browse/DRILL-580
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>         Attachments: DRILL-580.2.patch
> Most of Drill logical and physical rules (implements RelOptRule) are essentially conversion
rules.  For conversion rule, it's not required to specify the child operand in the rule's
pattern matching expression. However, currently, Drill logical or physical rules specify the
child operand. This will cause unnecessary rule firing during optiq transformation call, causing
more planning time. 
> In stead, for conversion rule in Drill logical/physical phases, it would be sufficient
enough to specify the parent operand.  

This message was sent by Atlassian JIRA

View raw message