Actually, the thing with the JSON plans is slightly different now: There are two types of plans:
1) The plan that describes the user program originally. That is what you get from env.getExecutionPlan(). In the Batch API, this has the result of the optimizer, in the streaming API the stream graph. 2) There is a JSON plan for the JobGraph / ExecutionGraph. This is what the web dashboard uses. The main difference to the other JSON plan is that in the JobGraph, not all operators are visible any more. Chained operations currently look like one operator to the JobGraph. Hence this JSON plan usually has fewer operators, and the names indicate that an operator is actually a chain of operations. Greetings, Stephan On Thu, Jan 14, 2016 at 6:15 PM, Fabian Hueske <fhue...@gmail.com> wrote: > @Christian: I don't think that is possible. > > There are quite a few things missing in the JSON including: > - User function objects (Flink ships objects not class names) > - Function configuration objects > - Data types > > Best, Fabian > > 2016-01-14 16:02 GMT+01:00 lofifnc <alexander.k...@mni.thm.de>: > >> Hi Márton, >> >> Thanks for your answer. But now I'm even more confused as it somehow >> conflicts with the documentation. ;) >> According to the wiki and the stratosphere paper the JobGraph will be >> submitted to the JobManager. And the JobManager will then translate it >> into >> the ExecutionGraph. >> >> > In order to track the status of the parallel vertex and channel >> > instances individually, the Job Manager spans the Job Graph >> > to the Execution Graph, as shown in Fig. 9. The Execution >> > Graph contains a node for each parallel instance of a vertex, >> > which we refer to as a task. >> >> So the ExecutionGraph should only be available at the JobManager and >> contain >> a node for each parallel instance of a operator and the corresponding >> vertices. >> >> The question is in the context of my master thesis as I'm trying to >> describe >> the deployment process of Flink. And wan't to use a visualization of the >> execution plan as an concrete example for one of these three Graphs. >> >> Best Alex! >> >> >> >> >> -- >> View this message in context: >> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Flink-Execution-Plan-tp4290p4297.html >> Sent from the Apache Flink User Mailing List archive. mailing list >> archive at Nabble.com. >> > >
