You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@gobblin.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2021/06/04 20:46:00 UTC
[jira] [Work logged] (GOBBLIN-1456) GobblinServiceJobScheduler
update logic
[ https://issues.apache.org/jira/browse/GOBBLIN-1456?focusedWorklogId=607310&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-607310 ]
ASF GitHub Bot logged work on GOBBLIN-1456:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 04/Jun/21 20:45
Start Date: 04/Jun/21 20:45
Worklog Time Spent: 10m
Work Description: arjun4084346 commented on pull request #3295:
URL: https://github.com/apache/gobblin/pull/3295#issuecomment-854988863
@sv2000 please merge
--
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:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 607310)
Remaining Estimate: 0h
Time Spent: 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: 10m
> 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)