You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Jing Chen (JIRA)" <ji...@apache.org> on 2017/09/30 02:07:01 UTC
[jira] [Commented] (AURORA-957) JobConfiguration should not contain
a cron schedule
[ https://issues.apache.org/jira/browse/AURORA-957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16186804#comment-16186804 ]
Jing Chen commented on AURORA-957:
----------------------------------
Hi Bill, I am kinda confused about the deprecation cycle here, I am wondering if we should make cron RPCs accept JobConfiguration and CronJobConfiguration or if we make cron RPCs accept CronJobConfiguration only after the patch.
> JobConfiguration should not contain a cron schedule
> ---------------------------------------------------
>
> Key: AURORA-957
> URL: https://issues.apache.org/jira/browse/AURORA-957
> Project: Aurora
> Issue Type: Story
> Components: Scheduler, Usability
> Reporter: Bill Farner
> Assignee: Jing Chen
>
> Cron behavior is treated as a composed characteristic of a job, so therefore it should not be a trait of jobs that are not cron. Create a new struct for cron jobs:
> {noformat}
> struct CronJobConfiguration {
> 1: string schedule
> 2: JobConfiguration job
> }
> {noformat}
> Change cron-related RPCs to accept this type instead of JobConfiguration (with a deprecation cycle), and remove cronSchedule from JobConfiguration.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)