[
https://issues.apache.org/jira/browse/AMBARI-15431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Beerbower updated AMBARI-15431:
-----------------------------------
Description:
Atlas configuration name {{application.properties}} has been changed to
{{atlas-application.properties}} to avoid name conflicts with other services.
See https://issues.apache.org/jira/browse/ATLAS-392.
Ambari scripts for Atlas currently use the configuration name
{{application.properties}} for all stack levels. Stacks which include Atlas >
0.5 should use the configuration name {{atlas-application.properties}}.
was:
Atlas conf needs to be included in other components for hooks. The name
resolution can conflict and hence properties filename should be atlas specific.
Ambari currently exposes the configuration application.properties which needs
to be renamed to atlas-application.properties. That change has already been
made in Atlas trunk. See https://issues.apache.org/jira/browse/ATLAS-392.
> Atlas Integration : Rename Atlas Configurations
> -----------------------------------------------
>
> Key: AMBARI-15431
> URL: https://issues.apache.org/jira/browse/AMBARI-15431
> Project: Ambari
> Issue Type: Bug
> Reporter: Tom Beerbower
> Assignee: Tom Beerbower
>
> Atlas configuration name {{application.properties}} has been changed to
> {{atlas-application.properties}} to avoid name conflicts with other services.
> See https://issues.apache.org/jira/browse/ATLAS-392.
> Ambari scripts for Atlas currently use the configuration name
> {{application.properties}} for all stack levels. Stacks which include Atlas
> > 0.5 should use the configuration name {{atlas-application.properties}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
