[
https://issues.apache.org/jira/browse/OOZIE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13818836#comment-13818836
]
Shwetha G S commented on OOZIE-1535:
------------------------------------
Issue: If there are multiple coords that are set-up for a cluster, and if there
are any changes in cluster endpoints(namenode/jt), each of the coord needs to
be updated with the new endpoint. Since oozie doesn't support updating these
properties, user should end the existing coords and create new coords with new
endpoints.
Proposal: Coord submit should optionally take hdfs path of a properties file
and should append these properties to the coord. Each materialisation should
read this property file if configured for the coord. Storing properties this
way external to the coord, helps with sharing it across coords and updating
easier.
Any thoughts/ideas?
> Update job properties for WF/COORD
> ----------------------------------
>
> Key: OOZIE-1535
> URL: https://issues.apache.org/jira/browse/OOZIE-1535
> Project: Oozie
> Issue Type: Improvement
> Reporter: Srikanth Sundarrajan
> Assignee: Shwetha G S
>
> It should be possible to update job submission properties for a running job,
> both for WF and COORD jobs. The updated properties would be used for all
> subsequent actions (not yet started).
--
This message was sent by Atlassian JIRA
(v6.1#6144)
