You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2019/09/18 07:55:00 UTC

[jira] [Closed] (FLINK-14067) Decouple PlanExecutor from JSON plan generation

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

Aljoscha Krettek closed FLINK-14067.
------------------------------------
    Fix Version/s: 1.10.0
       Resolution: Implemented

Implemented on master in e2728c0dddafcfe7fac0652084be6c7fd9714d85 and previous commits.

> Decouple PlanExecutor from JSON plan generation
> -----------------------------------------------
>
>                 Key: FLINK-14067
>                 URL: https://issues.apache.org/jira/browse/FLINK-14067
>             Project: Flink
>          Issue Type: Sub-task
>          Components: API / DataSet, Client / Job Submission
>            Reporter: Aljoscha Krettek
>            Assignee: Aljoscha Krettek
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> {{PlanExecutor}} has a method {{getOptimizerPlanAsJSON()}} that is used by DataSet environments to get a JSON version of the execution plan. To ease future work and to make it more maintainable we should get rid of that method and instead have a dedicated utility for generating JSON plans that the environments can use.
> (The only reason this method is on the executor is because only {{flink-clients}} via {{flink-optimizer}} has the required components to derive a JSON plan.)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)