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 07:48:58 UTC

[jira] [Created] (AMBARI-18891) Oozie config not shown as stale upon changing DefaultFS

Sebastian Toader created AMBARI-18891:
-----------------------------------------

             Summary: 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


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)