[
https://issues.apache.org/jira/browse/GOBBLIN-2200?focusedWorklogId=967195&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-967195
]
ASF GitHub Bot logged work on GOBBLIN-2200:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 23/Apr/25 08:42
Start Date: 23/Apr/25 08:42
Worklog Time Spent: 10m
Work Description: pratapaditya04 commented on code in PR #4108:
URL: https://github.com/apache/gobblin/pull/4108#discussion_r2055553678
##########
gobblin-api/src/main/java/org/apache/gobblin/configuration/ConfigurationKeys.java:
##########
@@ -1047,6 +1047,12 @@ public class ConfigurationKeys {
public static final String AZKABAN_FLOW_ID = "azkaban.flow.flowid";
public static final String AZKABAN_JOB_ID = "azkaban.job.id";
public static final String AZKABAN_EXEC_ID = "azkaban.flow.execid";
+ // Configuration Key for setting a unique job execution identifier in GaaS,
the value is a UUID
+ public static final String GAAS_JOB_EXEC_ID = "gaas.job.execid";
+
+ // Configuration Key for storing hash of gaas.job.execid, to be used as
jobExecutionId(integer) for backwards compatibility
+ public static final String GAAS_JOB_EXEC_ID_HASH =
"gaas.job.executionid.hash";
Review Comment:
The com.typesafe.config maintains config in hierarichal structure, so it
maintains same paths, in the same structure, for it to distinguish
.withValue(ConfigurationKeys.GAAS_JOB_EXEC_ID_HASH,
ConfigValueFactory.fromAnyRef(gaasJobExecutionIdHash))
.withoutPath())
```
it would have been needed to add the config like this, but
In general, it is not recommended to keep two configuration keys with the
same base name (e.g., a.key1 and a.key1.hash) because this can lead to
ambiguity and conflicts within the configuration management system.
```
##########
gobblin-api/src/main/java/org/apache/gobblin/configuration/ConfigurationKeys.java:
##########
@@ -1047,6 +1047,12 @@ public class ConfigurationKeys {
public static final String AZKABAN_FLOW_ID = "azkaban.flow.flowid";
public static final String AZKABAN_JOB_ID = "azkaban.job.id";
public static final String AZKABAN_EXEC_ID = "azkaban.flow.execid";
+ // Configuration Key for setting a unique job execution identifier in GaaS,
the value is a UUID
+ public static final String GAAS_JOB_EXEC_ID = "gaas.job.execid";
+
+ // Configuration Key for storing hash of gaas.job.execid, to be used as
jobExecutionId(integer) for backwards compatibility
+ public static final String GAAS_JOB_EXEC_ID_HASH =
"gaas.job.executionid.hash";
Review Comment:
The com.typesafe.config maintains config in hierarichal structure, so it
maintains same paths, in the same structure, for it to distinguish .```
withValue(ConfigurationKeys.GAAS_JOB_EXEC_ID_HASH,
ConfigValueFactory.fromAnyRef(gaasJobExecutionIdHash))
.withoutPath())
```
```
it would have been needed to add the config like this, but
In general, it is not recommended to keep two configuration keys with the
same base name (e.g., a.key1 and a.key1.hash) because this can lead to
ambiguity and conflicts within the configuration management system.
```
Issue Time Tracking
-------------------
Worklog Id: (was: 967195)
Time Spent: 1h 40m (was: 1.5h)
> 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 40m
> 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)
