[
https://issues.apache.org/jira/browse/SLIDER-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124298#comment-14124298
]
ASF subversion and git services commented on SLIDER-402:
--------------------------------------------------------
Commit 486ef84f4cb7e6e716e70a82ac08e1c43b3c497d in incubator-slider's branch
refs/heads/develop from [~sumitmohanty]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-slider.git;h=486ef84 ]
SLIDER-181. Storm package updates (changes to accomodate storm script changing
to be a shell script from python)
SLIDER-402. Add support for general purpose cross referencing of named
properties (handle multiple replacements for single property)
> Add support for general purpose cross referencing of named properties
> ---------------------------------------------------------------------
>
> Key: SLIDER-402
> URL: https://issues.apache.org/jira/browse/SLIDER-402
> Project: Slider
> Issue Type: Bug
> Components: agent-provider, app-package
> Affects Versions: Slider 0.50
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
>
> We need to make sure that whatever syntax we have for cross referencing
> continues to work even as we look at adding more sources of configuration
> data.
> *examples*: sysprops, late binding information from the registry to link to
> other components.
> We may need to do something more typed, eg
> {attr:property}
> or even maybe {@property}, {@/global/property} to indicate attributes. And
> maybe even cross reference internal/resources
> size:"{@//resources/components/regions/yarn.component.instances}"
> Other references we could do with another syntax in the {}. Example
> {env:Path}, {sysprop:java.home}
> We'll need to allow for the { to be escaped somehow.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
