[
https://issues.apache.org/jira/browse/GOBBLIN-1970?focusedWorklogId=894189&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-894189
]
ASF GitHub Bot logged work on GOBBLIN-1970:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Dec/23 01:34
Start Date: 06/Dec/23 01:34
Worklog Time Spent: 10m
Work Description: umustafi commented on PR #3841:
URL: https://github.com/apache/gobblin/pull/3841#issuecomment-1841933228
https://github.com/umustafi/gobblin/pull/13/checks?sha=8553a62e7965439e10f47ec5a91d91f686aff099
checks on my fork
Issue Time Tracking
-------------------
Worklog Id: (was: 894189)
Time Spent: 2h 10m (was: 2h)
> Consolidate Processing Dag Actions to Single Code Path
> ------------------------------------------------------
>
> Key: GOBBLIN-1970
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1970
> Project: Apache Gobblin
> Issue Type: Improvement
> Components: gobblin-service
> Reporter: Urmi Mustafi
> Assignee: Abhishek Tiwari
> Priority: Major
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> We have similar code in the DagActionStoreChangeMonitor and DagManager to
> process dag actions from the DagActionStore. There have been small
> discrepancies between the code in each area leading to unexpected bugs in how
> the actions are processed, so to fix forward and make this easier to maintain
> with code in one place we consolidate all logic relating to the dag action
> processing to the DagActionStoreChangeMonitor. The processing in the change
> monitor is working correctly, while the handling of launch events in the
> DagManager is failing compilation most likely due to an error loading the job
> templates when initializing the compiler but we're not able to identify the
> exact issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
