[
https://issues.apache.org/jira/browse/GOBBLIN-1821?focusedWorklogId=858512&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-858512
]
ASF GitHub Bot logged work on GOBBLIN-1821:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Apr/23 20:56
Start Date: 21/Apr/23 20:56
Worklog Time Spent: 10m
Work Description: ZihanLi58 commented on code in PR #3684:
URL: https://github.com/apache/gobblin/pull/3684#discussion_r1174157360
##########
gobblin-utility/src/main/java/org/apache/gobblin/util/JobLauncherUtils.java:
##########
@@ -68,6 +68,16 @@ public static String newJobId(String jobName) {
return Id.Job.create(jobName, System.currentTimeMillis()).toString();
}
+ /**
+ * Create a new job ID from a flow execution ID.
+ *
+ * @param jobName job name
+ * @return new job ID
+ */
+ public static String newJobId(String jobName, long flowId) {
Review Comment:
public static String newJobId(String jobName, long executionId) ?
Issue Time Tracking
-------------------
Worklog Id: (was: 858512)
Remaining Estimate: 0h
Time Spent: 10m
> Allow flow execution ID from GaaS to propagate into job IDs from Gobblin
> Cluster
> --------------------------------------------------------------------------------
>
> Key: GOBBLIN-1821
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1821
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-cluster
> Reporter: William Lo
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When Gobblin-as-a-Service sends a job to Gobblin cluster, the Gobblin cluster
> will create a new Job ID to identify the job. This makes it difficult to
> associate the job with the flow that kicked off the job in
> Gobblin-as-a-Service. Given this, it makes it difficult to associate jobs
> with the flow that sent them.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
