[
https://issues.apache.org/jira/browse/FLINK-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991514#comment-14991514
]
ASF GitHub Bot commented on FLINK-2966:
---------------------------------------
Github user rmetzger commented on a diff in the pull request:
https://github.com/apache/flink/pull/1327#discussion_r43998970
--- Diff: flink-runtime-web/web-dashboard/app/scripts/common/filters.coffee
---
@@ -28,6 +28,32 @@ angular.module('flinkApp')
amDurationFormatExtendedFilter
+.filter "humanizeDuration", ->
--- End diff --
Sorry that I've asked about this. As a committer I have to make sure we
properly mark copied code, and this functionality is something very commonly
used, and I'm sure there are plenty of implementations of this around in the
web.
To be honest, I would have probably copied it from somewhere. That's why I
was checking, just to make sure.
> Improve the way job duration is reported on web frontend.
> ---------------------------------------------------------
>
> Key: FLINK-2966
> URL: https://issues.apache.org/jira/browse/FLINK-2966
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Reporter: Sachin Goel
> Assignee: Sachin Goel
> Priority: Minor
>
> Right now, job duration is always reported in milliseconds. For long running
> jobs, this is not the best way.
> We should incorporate some kind of granularity in this. I propose this:
> 0-60 s : as x ms
> 60-3600 s: as x min y s
> 3600-86400 s: as x h y min [report as x h y min z s on hover]
> > 86400 s: as x d y h [report as x d y h z min t s on hover]
> I will start working on this, and we can change the granularity if someone
> has a better idea.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
