[
https://issues.apache.org/jira/browse/AURORA-964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14240359#comment-14240359
]
Maxim Khutornenko commented on AURORA-964:
------------------------------------------
The idea of using a scheduler updater to create jobs is quite entertaining and
would definitely help us with the linked AURORA-932. My only concern is that
client detection of create vs. update path (i.e. for wiring up client hooks) is
going to be a bit more complex and non-atomical.
> 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)
