flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timo Walther (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4565) Support for SQL IN operator
Date Tue, 06 Sep 2016 13:11:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15467383#comment-15467383

Timo Walther commented on FLINK-4565:

tableEnv.sql(...) returns a Table containing a LogicalRelNode (which is a LogicalNode and
just wraps RelNodes; Calcite already did the validation). The Table API returns Tables containing
specific LogicalNodes depending on the operation (Table API does the validation). All LogicalNodes
have a "construct" method translating the Flink logical operators to Calcites RelNode representation
for optimization. The magic happens in Batch/StreamTableEnvironment.translate() where the
RelNodes are optimized using a specific set of rules and converted to "DataSet/DataStreamRel"s
also by using specific rules.

> 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

View raw message