[
https://issues.apache.org/jira/browse/GOBBLIN-1456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudarshan Vasudevan resolved GOBBLIN-1456.
------------------------------------------
Fix Version/s: 0.16.0
Resolution: Fixed
Issue resolved by pull request #3295
[https://github.com/apache/gobblin/pull/3295]
> 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
> Fix For: 0.16.0
>
> 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)
