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

Flink Jira Bot updated FLINK-9453:
----------------------------------
    Labels: auto-unassigned stale-major  (was: auto-unassigned)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help 
the community manage its development. I see this issues has been marked as 
Major but is unassigned and neither itself nor its Sub-Tasks have been updated 
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this 
ticket is a Major, please either assign yourself or give an update. Afterwards, 
please remove the label or in 7 days the issue will be deprioritized.


> Flink 1.5 incorrectly shows statistics in web UI
> ------------------------------------------------
>
>                 Key: FLINK-9453
>                 URL: https://issues.apache.org/jira/browse/FLINK-9453
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Web Frontend
>    Affects Versions: 1.5.0
>            Reporter: Andrei Shumanski
>            Priority: Major
>              Labels: auto-unassigned, stale-major
>         Attachments: Flink_1.4.PNG, Flink_1.5.PNG
>
>
> Flink 1.5.0 incorrectly shows execution statistics and differently from Flink 
> 1.4.1.
> I attach screenshots from both versions. It looks like 1.5.0 sums all steps 
> in operators connected with "forward()". It makes it impossible to understand 
> how much data was actually consumed.
> My test code:
>  
> {code:java}
> public static void main(String[] args) throws Exception {
> StreamExecutionEnvironment env = 
> StreamExecutionEnvironment.getExecutionEnvironment();
> List<Integer> input = new ArrayList<>();
> input.add(1);
> input.add(2);
> input.add(3);
> input.add(4);
> input.add(5);
> DataStream<Integer> stream = env.fromCollection(input).rebalance();
> stream.map(i -> i+1).name("incr").forward().map(i -> 
> i-1).name("decr").forward().print();
> env.execute();
> }
> {code}
>  



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

Reply via email to