You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Timo Walther (JIRA)" <ji...@apache.org> on 2017/08/04 09:05:00 UTC

[jira] [Updated] (FLINK-7272) Support SQL IN with more than 20 elements in streaming

     [ https://issues.apache.org/jira/browse/FLINK-7272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timo Walther updated FLINK-7272:
--------------------------------
    Description: 
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.

  was: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.


> 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 API & SQL
>    Affects Versions: 1.3.1
>            Reporter: Timo Walther
>
> 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
(v6.4.14#64029)