[
https://issues.apache.org/jira/browse/AURORA-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15471614#comment-15471614
]
Renan DelValle commented on AURORA-1739:
----------------------------------------
Good to hear that, I'll gear up the patch then.
Unfortunately non-pointer variables can't be set to nil :/
In Go all variables have a zero value, in the case of string, its the empty
string which will cause the scheduler to always think that {{cronScheduler}} is
set.
Changing the type to optional causes {{cronScheduler}} to be generated as a
pointer which indeed can be set to nil.
> createJob thrift api for golang consistenly failing with empty CronSchedule
> ---------------------------------------------------------------------------
>
> Key: AURORA-1739
> URL: https://issues.apache.org/jira/browse/AURORA-1739
> Project: Aurora
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.15.0
> Reporter: Jimmy Wu
> Priority: Critical
>
> trying to create non cron job via the thrift api for golang but consistently
> getting error "Cron jobs may only be created/updated by calling
> scheduleCronJob.". Root cause : CronSchedule is not set in JobConfiguration
> hence an empty string is used, then create job request gets rejected because
> aurora now treats empty cron schedule as failure (related changes
> https://reviews.apache.org/r/28571/). This issue breaks all createJob
> requests submitted from golang thrift api because empty string is default
> value for string instead of nil.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
