[
https://issues.apache.org/jira/browse/FLINK-20674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nico Kruber closed FLINK-20674.
-------------------------------
Resolution: Duplicate
Yes, you are right [~pnowojski] this is probably more of a special case for
FLINK-18808. Naming the metric "Records produced" may help to some extend, but
this also applies to bytes. Also, if you want to debug network load, you
actually want to see how much data is sent. (ok, maybe you can read that from
the bytes received instead but complex communication patterns also make that
confusing)
> Wrong send/received stats with UNION ALL
> ----------------------------------------
>
> Key: FLINK-20674
> URL: https://issues.apache.org/jira/browse/FLINK-20674
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / Runtime
> Affects Versions: 1.12.0, 1.11.3
> Reporter: Nico Kruber
> Priority: Major
>
> When using {{UNION ALL}} to union the same table twice , the number of
> records and bytes sent is just half of what the next task receives:
> Reproducible with this:
> {code}
> CREATE TEMPORARY TABLE test (
> `number` SMALLINT
> )
> WITH (
> 'connector' = 'datagen',
> 'rows-per-second' = '1'
> );
> SELECT * FROM (
> (SELECT * FROM test)
> UNION ALL
> (SELECT * FROM test)
> )
> {code}
> Arguably, the use case is not too useful but other combinations may be
> affected, too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
