[
https://issues.apache.org/jira/browse/FLINK-14437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17358377#comment-17358377
]
Timo Walther commented on FLINK-14437:
--------------------------------------
Hi [~jark], yes supporting batch mode in {{StreamTableEnvironment}} has high
priority and will happen in the next 1-2 weeks. It was not explicitly mentioned
in FLIP-136 but is already considered in the subtask FLINK-20897. I decided for
dropping legacy early in the new release cycle but after this is completed in a
couple of days, the development on FLIP-136 will continue and should be
included in 1.14.
> Drop the legacy planner
> -----------------------
>
> Key: FLINK-14437
> URL: https://issues.apache.org/jira/browse/FLINK-14437
> Project: Flink
> Issue Type: Technical Debt
> Components: Table SQL / Legacy Planner
> Reporter: Timo Walther
> Assignee: Timo Walther
> Priority: Major
>
> This is an umbrella issue for all tasks that are related to dropping the
> legacy planner.
> It assumes that the community has chosen the Blink planner as the new default
> planner for Table and SQL programs.
> As discussed in
> https://lists.apache.org/thread.html/r0851e101e37fbab273775b6a252172c7a9f7c7927107c160de779831%40%3Cdev.flink.apache.org%3E
> we will perform the following steps in 1.14:
> - Drop `flink-table-planner` early
> - Drop many deprecated interfaces and API on demand
> - Rename `flink-table-planner-blink` to `flink-table-planner`
> - Rename `flink-table-runtime-blink` to `flink-table-runtime`
> - Remove references of "Blink" in the code base
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
