[
https://issues.apache.org/jira/browse/FLINK-3944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15327687#comment-15327687
]
Fabian Hueske commented on FLINK-3944:
--------------------------------------
I will open a PR to revert the commit.
> Add optimization rules to reorder Cartesian products and joins
> --------------------------------------------------------------
>
> Key: FLINK-3944
> URL: https://issues.apache.org/jira/browse/FLINK-3944
> Project: Flink
> Issue Type: Bug
> Components: Table API
> Affects Versions: 1.1.0
> Reporter: Fabian Hueske
> Assignee: Fabian Hueske
> Priority: Critical
> Fix For: 1.1.0
>
>
> Currently, we do not support the execution of Cartesian products.
> Because we do not optimize the order of joins (due to missing statistics),
> joins are executed in the order in which they are specified. This works well
> for the Table API, however it can be problematic in case of SQL queries where
> the order of tables in the FROM clause should not matter.
> In case of SQL queries, it can happen that the optimized plan contains
> Cartesian products because joins are not reordered. If we add optimization
> rules that switch Cartesian products and joins, such situations can be
> resolved.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
