[
https://issues.apache.org/jira/browse/GOBBLIN-2200?focusedWorklogId=966948&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-966948
]
ASF GitHub Bot logged work on GOBBLIN-2200:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 21/Apr/25 14:03
Start Date: 21/Apr/25 14:03
Worklog Time Spent: 10m
Work Description: pratapaditya04 commented on code in PR #4108:
URL: https://github.com/apache/gobblin/pull/4108#discussion_r2052423286
##########
gobblin-modules/gobblin-azkaban/src/main/java/org/apache/gobblin/azkaban/AzkabanJobLauncher.java:
##########
@@ -385,7 +385,11 @@ private boolean isCurrentTimeInRange() {
*/
private static List<? extends Tag<?>> addAdditionalMetadataTags(Properties
jobProps) {
List<Tag<?>> metadataTags = Lists.newArrayList();
- String jobExecutionId = jobProps.getProperty(AZKABAN_FLOW_EXEC_ID, "");
+ String jobExecutionId =
jobProps.getProperty(ConfigurationKeys.GAAS_JOB_EXEC_ID_HASH, "");
Review Comment:
Yeah , we will use the same class
Issue Time Tracking
-------------------
Worklog Id: (was: 966948)
Time Spent: 1h 10m (was: 1h)
> Moving Away From Azkaban Execution Id
> -------------------------------------
>
> Key: GOBBLIN-2200
> URL: https://issues.apache.org/jira/browse/GOBBLIN-2200
> Project: Apache Gobblin
> Issue Type: Improvement
> Reporter: Aditya Pratap Singh
> Priority: Major
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> Moving Away From Azkaban Execution Id
> In several places we use azkaban.flow.exec.id config values to identify the
> jobExecution, since we don't want to tie Gobblin to Azkaban, introducing a
> new field
> gaas.job.execid which will serve as the configuration Key for a unique job
> execution identifier in GaaS, the value is a UUID
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
