[ 
https://issues.apache.org/jira/browse/GOBBLIN-2097?focusedWorklogId=924036&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-924036
 ]

ASF GitHub Bot logged work on GOBBLIN-2097:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 23/Jun/24 20:00
            Start Date: 23/Jun/24 20:00
    Worklog Time Spent: 10m 
      Work Description: umustafi commented on PR #3984:
URL: https://github.com/apache/gobblin/pull/3984#issuecomment-2185307923

   checks on my branch https://github.com/umustafi/gobblin/pull/29/checks




Issue Time Tracking
-------------------

    Worklog Id:     (was: 924036)
    Time Spent: 40m  (was: 0.5h)

> Use unique JobDataMaps and Properties to use for reminder events
> ----------------------------------------------------------------
>
>                 Key: GOBBLIN-2097
>                 URL: https://issues.apache.org/jira/browse/GOBBLIN-2097
>             Project: Apache Gobblin
>          Issue Type: Bug
>          Components: gobblin-service
>            Reporter: Urmi Mustafi
>            Assignee: Abhishek Tiwari
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> We notice that after deploying the service all subsequent scheduler triggers 
> after the very first one are incorrectly marked as reminders even when they 
> are for "original" events. This is a result of re-using the same JobDataMap 
> and Properties object between the original and reminder Jobs for the 
> Scheduler. The following changes create deep copies of both to use for the 
> reminders so adding a reminder flag in one will not affect the other. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to