You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Fabian Hueske (JIRA)" <ji...@apache.org> on 2016/03/16 16:17:33 UTC

[jira] [Commented] (FLINK-3507) PruneEmptyRules does not prune empty node as expected.

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

Fabian Hueske commented on FLINK-3507:
--------------------------------------

The {{PruneEmptyRules}} only match against an {{Values.IS_EMPTY}} operator. We would need to add a rule that generates such an {{Values.IS_EMPTY}} operator for predicates which are always false.
Right now, we do not have a runtime equivalent of {{{{Values.IS_EMPTY}}, so we could not execute such a plan.

> PruneEmptyRules does not prune empty node as expected. 
> -------------------------------------------------------
>
>                 Key: FLINK-3507
>                 URL: https://issues.apache.org/jira/browse/FLINK-3507
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API
>            Reporter: Chengxiang Li
>            Priority: Minor
>
> {noformat}
> val t = CollectionDataSets.get3TupleDataSet(env).as('a, 'b, 'c)
>       .where(Literal(false))
>       .groupBy('b)
>       .select('a.sum)
> {noformat}
> With PruneEmptyRules instances enabled, we expect the empty Aggregate and Project should be removed, while it's not removed after logical optimization.



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