[
https://issues.apache.org/jira/browse/SLIDER-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15198140#comment-15198140
]
ASF subversion and git services commented on SLIDER-1086:
---------------------------------------------------------
Commit 889934d35f6166f689d85be6530bd4980933e226 in incubator-slider's branch
refs/heads/feature/SLIDER-906_docker_support from [~jmaron]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=889934d ]
SLIDER-1086 add ability to propagate application properties into registry
service records
> Allow application configuration properties with specific prefix to propagate
> into registry service record as attributes
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: SLIDER-1086
> URL: https://issues.apache.org/jira/browse/SLIDER-1086
> Project: Slider
> Issue Type: New Feature
> Components: appmaster, registry
> Affects Versions: Slider 0.90.2
> Reporter: Jonathan Maron
> Assignee: Jonathan Maron
>
> It would be convenient to support the availability of application specific
> information from the YARN registry. This proposal is that application
> configuration properties with a specific prefix (e.g.
> "slider.service.record") get propagated by the AM into the service records
> registered for the application during its deployment.
> One question: should the attributes simply propagate into both the
> application and container service records, or should the properties have a
> mechanism for distinguishing between the two ("slider.app.service.record"
> prefix vs "slider.container.service.record", for example)?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
