[
https://issues.apache.org/jira/browse/AURORA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240343#comment-14240343
]
Bill Farner commented on AURORA-964:
------------------------------------
Thanks for filing, i fully agree that we need to choose our path here.
Personally, i'm in favor of embracing that this fell out of the design, but
interested to hear other opinions.
> Scheduler updater successfully updates a non-existent job
> ---------------------------------------------------------
>
> Key: AURORA-964
> URL: https://issues.apache.org/jira/browse/AURORA-964
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Reporter: Maxim Khutornenko
>
> As it's currently implemented, the scheduler updater ({{aurora beta-update
> start}}) creates a new job when an attempt is made to update a non-existent
> job. We should either prevent this from happening or fully embrace the idea
> of creating a job via server updater, deprecate {{createJob}} RPC and update
> related client commands.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
