[
https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467236#comment-15467236
]
Simone Robutti commented on FLINK-4565:
---------------------------------------
Ok, the testing part seems easy and straightforward. I'm still missing a part
of this whole process. For what I saw, the tableEnv.sql(...) is parsed by
Calcite and it returns a SqlRelNode, while the Table API translates the calls
and expressions to a LogicalNode. Both are then translated to an execution plan
to be executed in the runtime. I can't really understand how and where this
happens. The `.plan` and `.runtime` package contains some of the things I was
expecting but I can't really follow the logic. Also, if "IN" is supported,
there should be a translation somewhere for this operator and I can't find it.
> 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
>
> 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.3.4#6332)
