[
https://issues.apache.org/jira/browse/FLINK-2118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15430310#comment-15430310
]
Renkai Ge edited comment on FLINK-2118 at 8/22/16 8:40 AM:
-----------------------------------------------------------
[~fhueske][~aljoscha]
operations end with '=' have special attribute that will re-interpretation the
expressions
http://scala-lang.org/files/archive/spec/2.11/06-expressions.html#assignment-operators
I think to solve this problem, we may need to replace the operator '==='
by{code} '!!!' or '=!='{code} or something like these.
was (Author: renkaige):
[~fhueske][~aljoscha]
operations end with '=' have special attribute that will re-interpretation the
expressions
http://scala-lang.org/files/archive/spec/2.11/06-expressions.html#assignment-operators
I think to solve this problem, we may need to replace the operator '===' by
'!!!' or '=!=' or something like these.
> Table API fails on composite filter conditions
> ----------------------------------------------
>
> Key: FLINK-2118
> URL: https://issues.apache.org/jira/browse/FLINK-2118
> Project: Flink
> Issue Type: Bug
> Components: Table API & SQL
> Affects Versions: 0.9
> Reporter: Fabian Hueske
>
> Having a composite filter conditions such as
> {code}
> myTable.filter('name !== "Pete" && 'name !== "Bob")
> {code}
> fails with the following error message:
> {code}
> ExpressionException: Non-boolean operand types String and String in Pete &&
> 'name
> {code}
> whereas
> {code}
> myTable.filter( ('name !== "Pete") && ('name !== "Bob") )
> {code}
> works.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
