[ https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110789#comment-16110789 ]
ASF GitHub Bot commented on FLINK-4565: --------------------------------------- Github user fhueske commented on a diff in the pull request: https://github.com/apache/flink/pull/4404#discussion_r130859046 --- Diff: flink-libraries/flink-table/src/test/scala/org/apache/flink/table/runtime/batch/sql/SetOperatorsITCase.scala --- @@ -260,4 +260,108 @@ class SetOperatorsITCase( val results = result.toDataSet[Row].collect() TestBaseUtils.compareResultAsText(results.asJava, expected) } + + @Test + def testInWithFilter(): Unit = { --- End diff -- Should we validate the feature with plan tests (`TableTestBase`) rather than runtime tests? The feature does not require new operators, just expressions which are tested by dedicated tests and joins which are also tested. > Support for SQL IN operator > --------------------------- > > Key: FLINK-4565 > URL: https://issues.apache.org/jira/browse/FLINK-4565 > Project: Flink > Issue Type: Improvement > Components: Table API & SQL > Reporter: Timo Walther > Assignee: Timo Walther > > It seems that Flink SQL supports the uncorrelated sub-query IN operator. But > it should also be available in the Table API and tested. -- This message was sent by Atlassian JIRA (v6.4.14#64029)