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-2943) Confusing Bytes/Records "read" and "write" labels in WebUI job view
Date Wed, 04 Nov 2015 10:30:27 GMT

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

ASF GitHub Bot commented on FLINK-2943:

Github user sachingoel0101 commented on the pull request:

    Ah. Apologies. Will separate 2903 related work.
    On Nov 4, 2015 3:52 PM, "Fabian Hueske" <notifications@github.com> wrote:
    > Thanks for the PR. I will try it out.
    > One general comment though. Can we please not merge several issues into a
    > single PR? The problem is that this breaks the automatic linking of PRs and
    > JIRA issues. In this case, FLINK-2903 will not receive any comments made on
    > this PR. Separate PRs for individual issues is also requested by our coding
    > guidelines
    > <http://flink.apache.org/contribute-code.html#coding-guidelines>.
    > —
    > Reply to this email directly or view it on GitHub
    > <https://github.com/apache/flink/pull/1323#issuecomment-153672870>.

> Confusing Bytes/Records "read" and "write" labels in WebUI job view
> -------------------------------------------------------------------
>                 Key: FLINK-2943
>                 URL: https://issues.apache.org/jira/browse/FLINK-2943
>             Project: Flink
>          Issue Type: Improvement
>          Components: Webfrontend
>    Affects Versions: 0.10
>            Reporter: Fabian Hueske
>              Labels: starter
>             Fix For: 0.10
> The job detail view of the WebUI shows the amount of data and records received from and
sent out by each individual operator. This information is very valuable, if correctly interpreted.

> However, the table headings for the corresponding columns ("Bytes read", "Records read",
"Bytes written", and "Records written") are confusing in my opinion because they do not indicate
that only incoming and outgoing data is tracked and disk IO is not considered at all. 
> For example, the UI shows no "Bytes/Records read" and only "Bytes/Records written" for
DataSources which I find counter-intuitive.
> I propose to rename these labels to either "X received" and "X sent" or "X incoming"
and "X outgoing" to make clear that this information only affects incoming and outgoing data.
> Opinions?

This message was sent by Atlassian JIRA

View raw message