You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sumit Mohanty (JIRA)" <ji...@apache.org> on 2013/09/16 06:56:53 UTC
[jira] [Updated] (AMBARI-3241) Add support for task specific custom
configuration
[ https://issues.apache.org/jira/browse/AMBARI-3241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sumit Mohanty updated AMBARI-3241:
----------------------------------
Attachment: AMBARI-3241
Added code changes for
* Ability to add additional config (or remove existing) on a per task basis
* Configuration modifications are stored along with config tags and when configuration is materialized it is modifed as necessary
* Added unit tests and modified few existing to add more validation
> Add support for task specific custom configuration
> ---------------------------------------------------
>
> Key: AMBARI-3241
> URL: https://issues.apache.org/jira/browse/AMBARI-3241
> Project: Ambari
> Issue Type: Bug
> Components: controller
> Affects Versions: 1.4.1
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Fix For: 1.4.1
>
> Attachments: AMBARI-3241
>
>
> All tasks, by default are associated with tags for each config type. There are some scenarios where individual tasks require customization beyond what is stored in the config. Example scenarios:
> * rca_enabled flag should only be set for job tracker
> * passwords should not be stored in client only site-configs
--
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