I used the following script to retrieve hbase-site.xml - so the value in my
first email did come from Slider:
tuple=`slider status $1 | grep "info.am.web.url"`
echo $tuple
FS=":"
url=`echo $tuple | awk '{split($0,array,": ")} END{print array[2]}'`
url="${url%,}"
url="${url%\"}"
url="${url#\"}"
url="${url}ws/v1/slider/publisher/slider/hbase-site.xml"
curl -k -o hbase-site.dnld $url
On Sun, Aug 3, 2014 at 8:47 AM, Jon Maron <jma...@hortonworks.com> wrote:
>
> On Aug 3, 2014, at 11:37 AM, Ted Yu <yuzhih...@gmail.com> wrote:
>
> > Hi,
> > I specified the following in appConfig.json:
> > "site.hbase-site.hbase.regionserver.info.port":
> > "${HBASE_REGIONSERVER.ALLOCATED_PORT}",
> >
> > After fetching effective hbase-site.xml from Slider hbase instance, I
> > noticed the following:
> >
> >
> <property><name>hbase.regionserver.info.port</name><value>${HBASE_REGIONSERVER.ALLOCATED_PORT}</value><source/></property>
> >
> > Has anyone else noticed similar issue ?
>
> What happens if you fetch it from slider itself? Is that one correct? I
> wonder if the in memory version simply isn’t being persisted?
>
> >
> > Cheers
>
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
