[
https://issues.apache.org/jira/browse/SLIDER-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202830#comment-15202830
]
Billie Rinaldi commented on SLIDER-851:
---------------------------------------
[~gsaha], for the unique.names case, an appConfig would look like the
following. You don't specify separate configs for A1, A2, and A3; you just
specify them for A, and the unique components will use A's configs. If the
COMPONENT_NAME or COMPONENT_ID variables are used, the unique components will
end up with slightly different configurations, as these variables are
substituted differently for each component instance.
{noformat}
{
"global": {
"global.property": "global.value"
},
"components": {
"A": {
"a.property": "a.value.${COMPONENT_NAME}.${COMPONENT_ID}"
}
}
}
{noformat}
> Support instance level configuration
> -------------------------------------
>
> Key: SLIDER-851
> URL: https://issues.apache.org/jira/browse/SLIDER-851
> Project: Slider
> Issue Type: New Feature
> Reporter: Siyuan Hua
> Attachments: SLIDER-851.1.patch, SLIDER-851.2.patch
>
>
> Use case, in kafka, component "broker" would have multiple instances running
> with some different configuration (for example, unique brokerid)
> There is no need to define different components for just different
> configurations
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
