You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by "shanyu zhao (JIRA)" <ji...@apache.org> on 2016/06/01 22:36:59 UTC

[jira] [Commented] (SLIDER-1135) Slider app XML configuration merge with existing configuration in package

    [ https://issues.apache.org/jira/browse/SLIDER-1135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15311267#comment-15311267 ] 

shanyu zhao commented on SLIDER-1135:
-------------------------------------

[~billie.rinaldi] the usage is that the storm tarball has storm-site.xml file, but we also want to modify some configurations that have been specified in the storm-site.xml file in the tarball at runtime. Currently if you specify storm-site configuration, it will completely replace the storm-site.xml in the tarball, so you have to specify all necessary configurations in app config.

> Slider app XML configuration merge with existing configuration in package
> -------------------------------------------------------------------------
>
>                 Key: SLIDER-1135
>                 URL: https://issues.apache.org/jira/browse/SLIDER-1135
>             Project: Slider
>          Issue Type: Bug
>            Reporter: shanyu zhao
>             Fix For: Slider 0.90.2
>
>         Attachments: SLIDER-1135.patch
>
>
> Today when you specify a configuration for a Slider app, e.g. in app_config you have: "site.storm-site.drpc.port": "1234", and in metainfo.xml you specify <configFile>, this would overwrite the existing storm-site.xml in the package. This forces you to set all storm configurations in app_config file.
> What we can do is to merge the provided configuration with existing conf files (storm-site.xml in this case).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)