[
https://issues.apache.org/jira/browse/FLINK-8387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timo Walther updated FLINK-8387:
--------------------------------
Description:
Code like the following looks correct but actually produces unintended side
effects:
{code}
left.join(right)
.where('a == 'd)
.select('a)
{code}
{{==}} is not converted into an expression but directly evaluated into a
boolean expression and implicitly converted into an {{false}} literal. Instead
of an exception this leads to an always rejecting table program. We should not
allow filters with {{false}} literals.
was:
Code like the following looks correct but actually produces unintended side
effects:
{code}
left.join(right)
.where('a == 'd)
.select('a)
{code}
{{==}} is not converted into an expression but directly evaluated into an
boolean expression and implicitly converted into an {{false}} literal. Instead
of an exception this leads to an always rejecting table program. We should not
allow filters with {{false}} literals.
> Do not allow filter(false)
> --------------------------
>
> Key: FLINK-8387
> URL: https://issues.apache.org/jira/browse/FLINK-8387
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Reporter: Timo Walther
> Assignee: Timo Walther
>
> Code like the following looks correct but actually produces unintended side
> effects:
> {code}
> left.join(right)
> .where('a == 'd)
> .select('a)
> {code}
> {{==}} is not converted into an expression but directly evaluated into a
> boolean expression and implicitly converted into an {{false}} literal.
> Instead of an exception this leads to an always rejecting table program. We
> should not allow filters with {{false}} literals.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)