[
https://issues.apache.org/jira/browse/AURORA-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14005155#comment-14005155
]
Mark Chu-Carroll commented on AURORA-408:
-----------------------------------------
Thinking about it a bit more: this will require changes to the client either
way:
Even if we can hijack them message field, the client only prints the contents
of that field if it's an error. So we'd be special-casing the use of the
message field in a killJob/createJob call. We'd have to modify the client now,
to have it print whatever is in that field; and then later, remove that,
because we don't want kill and create to have behavior inconsistent with other
commands.
If we're going to need to modify the client both before and after the
deprecation, we might as well not start special-casing the use of the message
field.
> Update client "job" commands to remove cron-related behavior.
> -------------------------------------------------------------
>
> Key: AURORA-408
> URL: https://issues.apache.org/jira/browse/AURORA-408
> Project: Aurora
> Issue Type: Task
> Components: Client
> Reporter: Mark Chu-Carroll
> Assignee: Mark Chu-Carroll
>
--
This message was sent by Atlassian JIRA
(v6.2#6252)
