[
https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15932933#comment-15932933
]
ASF GitHub Bot commented on FLINK-4565:
---------------------------------------
Github user twalthr commented on the issue:
https://github.com/apache/flink/pull/3502
Hi @DmytroShkvyra,
as I mentioned earlier, the first thing we should fix in this PR is using
more of Calcite capabilities. Calcite provides a `SubQueryRemoveRule` and
according to the Javadoc this is exaclty what we need in order to properly
support the IN for non-literals.
```
Transform that converts IN, EXISTS and scalar sub-queries into joins.
```
But I'm fine with focusing on literals first, if you like.
In general, creating objects in streaming applications is always very
expensive as they have to be garbage collected which affects latency and
throughput. BigDecimal should be avoided at all times and only be used if it is
really necessary.
> 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: Dmytro Shkvyra
>
> 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.15#6346)
