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

Posted to issues@flink.apache.org by "Jark Wu (JIRA)" <ji...@apache.org> on 2019/07/29 13:31:00 UTC

[jira] [Resolved] (FLINK-13447) Change default planner to legacy planner instead of any one

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

Jark Wu resolved FLINK-13447.
-----------------------------
       Resolution: Fixed
    Fix Version/s: 1.10.0

Fixed in 1.10.0: 5b01e7139c1d0307e93f0e448e75ee6b5e6541ca
Fixed in 1.9.0: c763cef2f0d244b305fc9e3c70be0d6c89d5eba5

> Change default planner to legacy planner instead of any one
> -----------------------------------------------------------
>
>                 Key: FLINK-13447
>                 URL: https://issues.apache.org/jira/browse/FLINK-13447
>             Project: Flink
>          Issue Type: Task
>          Components: Table SQL / API
>    Affects Versions: 1.9.0
>            Reporter: Jark Wu
>            Assignee: Jark Wu
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 1.9.0, 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> As discussed in FLINK-13399, we will change the default behavior of the {{EnvironmentSettings}} to use old planner instead of any planner. This will enable us to have both planner in the classpath. This will also enable users/connectors to have both planner in dependency and without  using {{EnvironmentSettings}}.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)