[ 
https://issues.apache.org/jira/browse/GOBBLIN-1510?focusedWorklogId=637169&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-637169
 ]

ASF GitHub Bot logged work on GOBBLIN-1510:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Aug/21 22:18
            Start Date: 11/Aug/21 22:18
    Worklog Time Spent: 10m 
      Work Description: aplex commented on a change in pull request #3358:
URL: https://github.com/apache/gobblin/pull/3358#discussion_r687232635



##########
File path: 
gobblin-restli/gobblin-flow-config-service/gobblin-flow-config-service-api/src/main/pegasus/org/apache/gobblin/service/JobStatistics.pdl
##########
@@ -27,6 +27,7 @@ record JobStatistics {
 
   /**
    * estimate of time left until job completion
+   * "X hours Y minutes Z seconds"
    */
-  estimatedSecondsToCompletion: long
+  estimatedTimeToCompletion: string

Review comment:
       Rest APIs can be consumed by applications written in any language. Java 
has  DurationFormatUtils.formatDurationWords, but I guess there is no 
counterpart in Python/Javascript that will be able to convert that string back 
to internal duration format.
   
   So, for API fields we should stick to formats that any programming language 
can handle. To make the progress reporting more nice, we can convert those 
seconds to human readable-message in the client app.
   
   For dates, there is actually an ISO standard 
https://en.wikipedia.org/wiki/ISO_8601 that is both human- and machine- 
readable. Unfortunately, the current rest of the API uses milliseconds to 
represent dates, and it's important to keep the API surface consistent. So, I 
don't think we should migrate to it at this point, but we can do in the next 
major API version. It also has a standard for duration, but it looks pretty 
wired and I haven't seen it in other Rest APIs. 




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 637169)
    Time Spent: 3h 20m  (was: 3h 10m)

> Fix Progress Reporting Behavior & Cleanup Logs
> ----------------------------------------------
>
>                 Key: GOBBLIN-1510
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-1510
>             Project: Apache Gobblin
>          Issue Type: Improvement
>          Components: gobblin-core, gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 3h 20m
>  Remaining Estimate: 0h
>
> # Currently, when a job approaches the end the progress can appear "stuck" at 
> 96-99% because the progress changes are only reported if they are larger than 
> the threshold (5%).
>  # Decrease number of logs 
>  # Format the estimated time left to be human readable "X hours Y min Z 
> seconds" rather than "40389 seconds"  



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

Reply via email to