[
https://issues.apache.org/jira/browse/GOBBLIN-1857?focusedWorklogId=872071&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-872071
]
ASF GitHub Bot logged work on GOBBLIN-1857:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 20/Jul/23 21:18
Start Date: 20/Jul/23 21:18
Worklog Time Spent: 10m
Work Description: Will-Lo merged PR #3719:
URL: https://github.com/apache/gobblin/pull/3719
Issue Time Tracking
-------------------
Worklog Id: (was: 872071)
Time Spent: 1h (was: 50m)
> Allow override key for job execution ID in Helix Gobblin Cluster
> ----------------------------------------------------------------
>
> Key: GOBBLIN-1857
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1857
> Project: Apache Gobblin
> Issue Type: Bug
> Components: gobblin-cluster
> Reporter: William Lo
> Assignee: Hung Tran
> Priority: Major
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Job Execution ID is automatically inferred from the flow execution ID if the
> job was orchestrated by Gobblin-as-a-Service. However, this can lead to bugs
> in conjunction with other job keys such as earlyStop, since it would create
> multiple planningJobs and job IDs sent to Helix. These jobs would then have
> the same execution ID which is rejected by Helix.
> When those configurations are set, we want to force the Gobblin cluster to
> default to creating the job execution ID from its timestamp.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
