phet commented on code in PR #4013:
URL: https://github.com/apache/gobblin/pull/4013#discussion_r1701618512


##########
gobblin-service/src/main/java/org/apache/gobblin/service/modules/spec/JobExecutionPlanListDeserializer.java:
##########
@@ -110,6 +110,8 @@ public List<JobExecutionPlan> deserialize(JsonElement json, 
Type typeOfT, JsonDe
 
       JobExecutionPlan jobExecutionPlan = new JobExecutionPlan(jobSpec, 
specExecutor);
       jobExecutionPlan.setExecutionStatus(executionStatus);
+      
jobExecutionPlan.setCurrentGeneration(serializedJobExecutionPlan.get(SerializationConstants.CURRENT_GENERATION_KEY).getAsInt());
+      
jobExecutionPlan.setCurrentAttempts(serializedJobExecutionPlan.get(SerializationConstants.CURRENT_ATTEMPTS_KEY).getAsInt());

Review Comment:
   on a meta level, this PR would be more cohesive as two, one for 
PENDING_RETRY and the other for (de)serialization



##########
gobblin-runtime/src/main/java/org/apache/gobblin/service/monitoring/FlowStatusGenerator.java:
##########
@@ -41,7 +41,7 @@
 @Slf4j
 public class FlowStatusGenerator {
   public static final List<String> FINISHED_STATUSES = 
Lists.newArrayList(ExecutionStatus.FAILED.name(),
-      ExecutionStatus.COMPLETE.name(), ExecutionStatus.CANCELLED.name());
+      ExecutionStatus.COMPLETE.name(), ExecutionStatus.CANCELLED.name(), 
ExecutionStatus.PENDING_RETRY.name());

Review Comment:
   this is used in a number of places. is it acceptable to change the semantics 
for all of them?  e.g. is it OK here in `MysqlDMStateStore`:
   ```
     public boolean hasRunningJobs(DagManager.DagId dagId) throws IOException {
       return getDagNodes(dagId).stream()
           .anyMatch(node -> 
!FlowStatusGenerator.FINISHED_STATUSES.contains(node.getValue().getExecutionStatus().name()));
     }
   ```
   ?



-- 
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.

To unsubscribe, e-mail: dev-unsubscr...@gobblin.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to