[
https://issues.apache.org/jira/browse/FLINK-7800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632815#comment-16632815
]
Xingcan Cui commented on FLINK-7800:
------------------------------------
As posted in the calcite mailing list before [Question about join plan
optimization in
Flink|https://lists.apache.org/thread.html/f40182397d393b4348a2658d256c87fd7566b8add0eef3642a152471@%3Cdev.calcite.apache.org%3E],
the manner to forbid some candidate plans is still confusing me and the
problem becomes even harder when considering the time attributes (i.e., we need
some pushing-down to get the equi-predicate, while that doesn't hold for time
attributes). Do you have any suggestions? [~fhueske] [~twalthr]
> Enable window joins without equi-join predicates
> ------------------------------------------------
>
> Key: FLINK-7800
> URL: https://issues.apache.org/jira/browse/FLINK-7800
> Project: Flink
> Issue Type: New Feature
> Components: Table API & SQL
> Affects Versions: 1.4.0
> Reporter: Fabian Hueske
> Assignee: Xingcan Cui
> Priority: Major
> Labels: pull-request-available
>
> Currently, windowed joins can only be translated if they have at least on
> equi-join predicate. This limitation exists due to the lack of a good cross
> join strategy for the DataSet API.
> Due to the window, windowed joins do not have to be executed as cross joins.
> Hence, the equi-join limitation does not need to be enforces (even though
> non-equi joins are executed with a parallelism of 1 right now).
> We can resolve this issue by adding a boolean flag to the
> {{FlinkLogicalJoinConverter}} rule to permit non-equi joins and add such a
> rule to the logical optimization set of the DataStream API.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
