[
https://issues.apache.org/jira/browse/BEAM-7927?focusedWorklogId=290919&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-290919
]
ASF GitHub Bot logged work on BEAM-7927:
----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Aug/19 01:33
Start Date: 08/Aug/19 01:33
Worklog Time Spent: 10m
Work Description: chadrik commented on pull request #9293: [BEAM-7927]
Add JobService.GetJobs to the job API
URL: https://github.com/apache/beam/pull/9293#discussion_r311824689
##########
File path: model/job-management/src/main/proto/beam_job_api.proto
##########
@@ -123,6 +126,22 @@ message CancelJobResponse {
JobState.Enum state = 1; // (required)
}
+// A subset of info provided by ProvisionApi.ProvisionInfo
+message JobInfo {
+ string job_id = 1; // (required)
+ string job_name = 2; // (required)
+ google.protobuf.Struct pipeline_options = 3; // (required)
+ JobState.Enum state = 4; // (required)
Review comment:
I debated whether or not to include the state here.
Reason for including it: It's cheap to get, and it's the kind of info that
any web client would want to provide when displaying an overview of jobs (see
flink web ui). Providing it obviates the need for these clients to issue a
followup query to get the state of each job.
Reason for excluding it: It's the only value here that is not an intrinsic,
immutable property of a job. i.e. it changes over time, and so conceptually,
including it means that the JobInfo becomes invalid over time. Removing it
would make it a close fit for `beam.runners.fnexecution.provisioning.JobInfo`.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 290919)
Time Spent: 0.5h (was: 20m)
> Add ability to get the list of submitted jobs from gRPC JobService
> ------------------------------------------------------------------
>
> Key: BEAM-7927
> URL: https://issues.apache.org/jira/browse/BEAM-7927
> Project: Beam
> Issue Type: New Feature
> Components: beam-model
> Reporter: Chad Dombrova
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> As a developer building a client for monitoring running jobs via the
> JobService, I want the ability to get a list of jobs – particularly their job
> ids – so that I can use this as an entry point for getting other information
> about a job already offered by the JobService, such as the pipeline
> definition, a stream of status changes, etc.
> Currently, the JobService is only useful if you already have a valid job id.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
