Github user fhueske commented on a diff in the pull request:
https://github.com/apache/flink/pull/652#discussion_r29796343
--- Diff:
flink-core/src/main/java/org/apache/flink/api/common/JobExecutionResult.java ---
@@ -47,12 +48,23 @@ public JobExecutionResult(JobID jobID, long netRuntime,
Map<String, Object> accu
* Gets the net execution time of the job, i.e., the execution time in
the parallel system,
* without the pre-flight steps like the optimizer.
*
- * @return The net execution time.
+ * @return The net execution time in milliseconds.
*/
public long getNetRuntime() {
return this.netRuntime;
}
+ /**
+ * Gets the net execution time of the job, i.e., the execution time in
the parallel system,
+ * without the pre-flight steps like the optimizer in a desired unit.
+ *
+ * @param desiredUnit the unit of the <tt>NetRuntime</tt>
+ * @return The net execution time in the desired unit.
+ */
+ public long elapsedNetRuntime(TimeUnit desiredUnit) {
--- End diff --
Hmm, good point. I was not aware of that.
@tillrohrmann Any particular reason why duration was changed from
milliseconds to seconds?
IMO, it would make sense to the time with a higher resolution and convert
it on need.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
