[
https://issues.apache.org/jira/browse/AMBARI-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628071#comment-13628071
]
Sumit Mohanty commented on AMBARI-1865:
---------------------------------------
[[email protected]], is it OK to leave the data in service config mapping
as is? Any harm if we delete those?
One question related to the feature itself. Earlier, we used to keep the
mapping between service_name and config_type (in serviceconfigmapping). It
seems, that in Condor we do not keep this information any more. How do we know
the mapping that MAPREDUCE is associated with mapred-site, global, core-site?
> Upgrade script should move service configs to cluster
> -----------------------------------------------------
>
> Key: AMBARI-1865
> URL: https://issues.apache.org/jira/browse/AMBARI-1865
> Project: Ambari
> Issue Type: Sub-task
> Affects Versions: 1.3.0
> Reporter: Nate Cole
> Assignee: Nate Cole
> Fix For: 1.3.0
>
> Attachments: AMBARI-1865.patch
>
>
> The Upgrade script should pull the current service level configs and make
> them the cluster defaults.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
