Dug further into this ... Appears that only the variables that expand to a
number are allowed :( ... I can add another port to it and that export
works
<value>${THIS_HOST}:${site.global.abc.http_port}:${site.
global.abc.some_other_port}</value>
This goes back to my earlier post asking why there is a limit to export
only host:port info at component level ....
From
http://slider.incubator.apache.org/docs/slider_specs/specifying_exports.html
- "Currently, only the host name and dynamically allocated port values can
be exported."
Can someone explain why this limit ? Even this is not enforced as I can add
any constant or export multiple ports - so not clear what is the reason
behind blocking publishing of any non-number info ...
Should I file a Jira for this ?
Thanks
Manoj
On Wed, Jan 6, 2016 at 11:30 AM, Manoj Samel <[email protected]>
wrote:
> Slider 0.80 on secured cluster. Each component exports its host/port and
> some other info
>
> I am looking @ exported values at
> http://host:1025/ws/v1/slider/publisher/slider/componentinstancedata
>
>
> 1 - Just export host/port - This works
>
> <componentExports>
> <componentExport>
> <name>my_info</name>
>
> <value>${THIS_HOST}:${site.global.abc.http_port}</value>
> </componentExport>
> </componentExports>
>
> 2 - Export host/port and ** APPEND some constant - This works
>
> <componentExports>
> <componentExport>
> <name>my_info</name>
>
> <value>${THIS_HOST}:${site.global.abc.http_port}:XYZ</value>
> </componentExport>
> </componentExports>
>
> 3 - Try host/port/other info derived from param. In this case,
> ${site.global.abc.http_port} gets evaluated correctly in export but
> ${site.global.abc.some_other_info} appears as is - that is it does not gets
> evaluated in export.
>
> <componentExports>
> <componentExport>
> <name>my_info</name>
>
>
> <value>${THIS_HOST}:${site.global.abc.http_port}:${site.global.abc.some_other_info}</value>
> </componentExport>
> </componentExports>
>
> Any thoughts on how to achieve this ?
>
> Thanks,
>
> Manoj
>
