[
https://issues.apache.org/jira/browse/BEAM-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16964223#comment-16964223
]
Chad Dombrova commented on BEAM-8523:
-------------------------------------
Looking at this a little more, it seems it would be pretty easy to stream out
the past state history from GetMessageStream after the connection is made.
This would make it easier on clients, since they would not have to concern
themselves about ordering and race conditions between calls to a hypothetical
GetMessageHistory and GetMessageStream (i.e what happens if a new event arrives
between calls? If GetMessageHistory is called first we get the new event in
both results, in the other order we miss the event).
For tracking the state transition events on the JobInvocation, what's the
preferred object for 2-tuples? I noticed javafx.Pair is not used anywhere in
the Beam code. Should I use beam.sdk.values.KV?
> 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)
