[
https://issues.apache.org/jira/browse/GOBBLIN-1456?focusedWorklogId=607380&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-607380
]
ASF GitHub Bot logged work on GOBBLIN-1456:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/21 23:43
Start Date: 04/Jun/21 23:43
Worklog Time Spent: 10m
Work Description: asfgit closed pull request #3295:
URL: https://github.com/apache/gobblin/pull/3295
--
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 607380)
Time Spent: 20m (was: 10m)
> GobblinServiceJobScheduler update logic
> ---------------------------------------
>
> Key: GOBBLIN-1456
> URL: https://issues.apache.org/jira/browse/GOBBLIN-1456
> Project: Apache Gobblin
> Issue Type: Bug
> Reporter: Arjun Singh Bora
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> GobblinServiceJobScheduler update logic first deletes the spec and then adds
> it back. I think it is unnecessary and also create an issue. During delete
> spec it calls Orchestrator remove code and that sends a delete call to spec
> executor, which is wrong, because flow spec is actually not intended to be
> deleted. On cluster side, it is forcing a state store deletion.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
