[
https://issues.apache.org/jira/browse/FLINK-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-7272:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Support SQL IN with more than 20 elements in streaming
> ------------------------------------------------------
>
> Key: FLINK-7272
> URL: https://issues.apache.org/jira/browse/FLINK-7272
> Project: Flink
> Issue Type: New Feature
> Components: Table SQL / API
> Affects Versions: 1.3.1
> Reporter: Timo Walther
> Priority: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> During the implementation of FLINK-4565 I noticed that an "IN" operation with
> more than 20 elements is converted into {{LogicalValues}} + {{LogicalJoin}}
> operation. Since this is not possible in streaming, we should add some rule
> that merges both operators either into a Correlate or Calc.
> This problem also occurs when null is contained in the testing set. So this
> should get higher priority.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
