You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Chad Dombrova (Jira)" <ji...@apache.org> on 2019/10/30 23:54:00 UTC
[jira] [Updated] (BEAM-8523) Add useful timestamp to job servicer
GetJobs
[ https://issues.apache.org/jira/browse/BEAM-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chad Dombrova updated BEAM-8523:
--------------------------------
Description:
As a user querying jobs with JobService.GetJobs, it would be useful if the JobInfo result contained timestamps indicating various state changes that may have been missed by a client. Useful timestamps include:
* submitted (prepared to the job service)
* started (executor enters the RUNNING state)
* completed (executor enters a terminal state)
was:
As a user querying jobs with JobService.GetJobs, it would be useful if the JobInfo result contained timestamps indicating various state changes that may have been missed by a client. Useful even timestamps include:
* submitted (prepared to the job service)
* started (executor enters the RUNNING state)
* completed (executor enters a terminal state)
> Add useful timestamp to job servicer GetJobs
> --------------------------------------------
>
> Key: BEAM-8523
> URL: https://issues.apache.org/jira/browse/BEAM-8523
> Project: Beam
> Issue Type: New Feature
> Components: beam-model
> Reporter: Chad Dombrova
> Assignee: Chad Dombrova
> Priority: Major
>
> As a user querying jobs with JobService.GetJobs, it would be useful if the JobInfo result contained timestamps indicating various state changes that may have been missed by a client. Useful timestamps include:
>
> * submitted (prepared to the job service)
> * started (executor enters the RUNNING state)
> * completed (executor enters a terminal state)
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)