flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-4623) Create Physical Execution Plan of a DataStream
Date Sat, 29 Oct 2016 04:32:58 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15617412#comment-15617412
] 

ASF GitHub Bot commented on FLINK-4623:
---------------------------------------

Github user wuchong commented on a diff in the pull request:

    https://github.com/apache/flink/pull/2720#discussion_r85633731
  
    --- Diff: flink-libraries/flink-table/src/test/scala/resources/testUnionStream0.out ---
    @@ -2,3 +2,21 @@
     LogicalUnion(all=[true])
       LogicalTableScan(table=[[_DataStreamTable_0]])
       LogicalTableScan(table=[[_DataStreamTable_1]])
    +
    +== Physical Execution Plan ==
    +Stage 1 : Data Source
    +	content : collect elements with CollectionInputFormat
    +
    +Stage 2 : Data Source
    +	content : collect elements with CollectionInputFormat
    +
    +	Stage 3 : Operator
    +		content : from: (count, word)
    +		ship_strategy : REBALANCE
    +		exchange_mode : null
    +
    +		Stage 4 : Operator
    +			content : from: (count, word)
    +			ship_strategy : REBALANCE
    +			exchange_mode : null
    --- End diff --
    
    It seems that the json execution plan generated from `env.getExecutionPlan` dosen't contain
the `exchange_mode` information. Could we remove this node in explain? 


> Create Physical Execution Plan of a DataStream
> ----------------------------------------------
>
>                 Key: FLINK-4623
>                 URL: https://issues.apache.org/jira/browse/FLINK-4623
>             Project: Flink
>          Issue Type: Improvement
>          Components: Table API & SQL
>            Reporter: Timo Walther
>            Assignee: Anton Solovev
>              Labels: starter
>
> The {{StreamTableEnvironment#explain(Table)}} command for tables of a {{StreamTableEnvironment}}
only outputs the abstract syntax tree. It would be helpful if the {{explain}} method could
also generate a string from the {{DataStream}} containing a physical execution plan.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message