[
https://issues.apache.org/jira/browse/SLIDER-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14124944#comment-14124944
]
Steve Loughran commented on SLIDER-402:
---------------------------------------
the full implementation here will need lots of thinking & testing, so will have
to be a slider 2.0 issue.
As an example problem: what if today's initial impl sees an other reference in
the property it resolves? Is that resolved too? Do we then detect loops, or
(simpler) keep going until the stack runs out. IF we support lazy evaluation,
does that also imply that references to a lazy attr become lazy transitively?
....
> 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)
