[
https://issues.apache.org/jira/browse/BEAM-8523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963645#comment-16963645
]
Chad Dombrova commented on BEAM-8523:
-------------------------------------
{quote}
Seems to make sense but we might as well just have all the job states have
timestamps and just have a list of state transitions returned as part of the
job info. The last element within the list would be the "latest" state.
{quote}
That's an interesting idea. In that case, I think it might make sense to have
a GetStateHistory method. This could be a pattern that we extend to
GetMessageStream as well. We're currently working on creating a beam log
service, e.g. backed by StackDriver, so GetMessageHistory could fit in really
well there.
That makes me wonder, is there an established gRPC pattern for getting stream
history? For example, is there a way for a server to automatically backfill
the missed messages when a late stream connection is established? Or is it
better to keep these as two separate endpoints?
> 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)
