[jira] [Commented] (BEAM-8523) Add useful timestamp to job servicer GetJobs

["Luke Cwik (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16965023#comment-16965023 ] 

Luke Cwik commented on BEAM-8523:
---------------------------------

Typically when you would connect you would want to give some lower bound to filter messages. For example GetJobStateRequest could become:

 
{code:java}
message GetJobStateRequest {
  string job_id = 1; // (required)
  // (Optional) If specified, only state transitions after
  // the provided timestamp will be provided.
  google.protobuf.Timestamp min_message_timestamp;
}
{code}
 

> 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
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> 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)