You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Sebastian Toader (JIRA)" <ji...@apache.org> on 2016/11/15 13:11:58 UTC
[jira] [Issue Comment Deleted] (AMBARI-18891) Oozie config not
shown as stale upon changing DefaultFS
[ https://issues.apache.org/jira/browse/AMBARI-18891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sebastian Toader updated AMBARI-18891:
--------------------------------------
Comment: was deleted
(was: Committed to trunk:
{code}
commit 7df30b172d88271ffa5300149a73e86bf330a912
Author: Toader, Sebastian <st...@hortonworks.com>
Date: Tue Nov 15 13:56:12 2016 +0100
AMBARI-18891. Oozie config not shown as stale upon changing DefaultFS. (stoader)
{code}
Committed to branch-2.5:
{code}
commit 7b45053549b8d3dc2cfc8cc4fee7683df075c585
Author: Toader, Sebastian <st...@hortonworks.com>
Date: Tue Nov 15 13:56:12 2016 +0100
AMBARI-18891. Oozie config not shown as stale upon changing DefaultFS. (stoader)
{code}
)
> Oozie config not shown as stale upon changing DefaultFS
> -------------------------------------------------------
>
> Key: AMBARI-18891
> URL: https://issues.apache.org/jira/browse/AMBARI-18891
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Reporter: Sebastian Toader
> Assignee: Sebastian Toader
> Priority: Critical
> Fix For: 2.5.0
>
> Attachments: AMBARI-18891.v1.patch
>
>
> Since Oozie has a dependency on configuration settings defined in core-site this has to be added to the it's dependencies list in the stack definition.
> Without this if a configuration setting is changed in core-site Oozie won't be flagged as having stale configs by Ambari thus the user won't know that Oozie service has to be restarted to pick up changes from the modified core-site.xml
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)