You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Jinfeng Ni (JIRA)" <ji...@apache.org> on 2015/03/26 20:29:53 UTC

[jira] [Updated] (CALCITE-648) ProjectMergeRule's description does not follow the new naming convention when it is used in force mode.

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

Jinfeng Ni updated CALCITE-648:
-------------------------------
    Attachment: 0001-CALCITE-648-Modify-ProjectMergeRule-description-to-f.patch

> ProjectMergeRule's description does not follow the new naming convention when it is used in force mode. 
> --------------------------------------------------------------------------------------------------------
>
>                 Key: CALCITE-648
>                 URL: https://issues.apache.org/jira/browse/CALCITE-648
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Jinfeng Ni
>            Assignee: Julian Hyde
>            Priority: Minor
>         Attachments: 0001-CALCITE-648-Modify-ProjectMergeRule-description-to-f.patch
>
>
> ProjectMergeRule's description does not follow the naming checking in RelOptRule, when it is used in force mode. As such, a RuntimeException will be thrown if we try to create a force mode ProjectMergeRule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)