[
https://issues.apache.org/jira/browse/OOZIE-1769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968893#comment-13968893
]
Purshotam Shah commented on OOZIE-1769:
---------------------------------------
User can change all control parameter, concurrency, execution, timeout and
throttle but not coordinator name, frequency, start time, end time and timezone.
> An option to update coord properties/definition
> -----------------------------------------------
>
> Key: OOZIE-1769
> URL: https://issues.apache.org/jira/browse/OOZIE-1769
> Project: Oozie
> Issue Type: Bug
> Reporter: Purshotam Shah
> Assignee: Purshotam Shah
> Attachments: OOZIE-1769-V5.patch
>
>
> To change the coord definition user can update coord definition in hdfs and
> issue a update command. Existing coordinator definition will be replaced by
> new definition. The refreshed coordinator
> would keep the same coordinator ID, state, and coordinator actions.
> User can also provide -dryrun to validate changes.
> All created coord action(including in waiting) will use old configuration.
> User can rerun actions with -refresh option, -refresh option will use new
> configuration to rerun coord action.
> Ex.
> 1. $ oozie job -update <coordID> -config
> examples/apps/aggregator/job.properties
> Will update coord definition and action.
> 2. $ oozie job -update <coordID>
> Will fetch coord definition path from bundle and update coord definition
--
This message was sent by Atlassian JIRA
(v6.2#6252)
