|
|
-
Getting hostname (or any environment variable) into *-site.xml files
Stephen Boesch 2012-10-12, 13:37
Hi, We are using a library with hdfs that uses custom properties inside the *-site.xml files. Instead of (a) hard-coding or (b) writing a "sed" script to update to the local hostnames on each deployed node, is there a mechanism to use environment variables?
<property> <name>custom.property</name> <value>${HOSTNAME}</value> </property> I have tried this and out of the box the string ${HOSTNAME} is used. Anyone have recommendation/solution on this?
thanks,
stephen b
-
Re: Getting hostname (or any environment variable) into *-site.xml files
Harsh J 2012-10-12, 15:39
The ${FOO} stuff can be replaced via JVM System Properties. I just explained this on another thread (a few mails ago).
So if your "library" JVM had a system property of -DHOSTNAME=donkeykong.com then ${HOSTNAME} will be replaced by donkeykong.com automatically.
Likewise, even using Tool as the entry point of your app will let you achieve the same via regular -D args.
Hope this helps!
On Fri, Oct 12, 2012 at 7:07 PM, Stephen Boesch <[EMAIL PROTECTED]> wrote: > Hi, > We are using a library with hdfs that uses custom properties inside the > *-site.xml files. Instead of (a) hard-coding or (b) writing a "sed" script > to update to the local hostnames on each deployed node, is there a mechanism > to use environment variables? > > <property> > <name>custom.property</name> > <value>${HOSTNAME}</value> > </property> > > > I have tried this and out of the box the string ${HOSTNAME} is used. Anyone > have recommendation/solution on this? > > thanks, > > stephen b
-- Harsh J
-
Re: Getting hostname (or any environment variable) into *-site.xml files
Stephen Boesch 2012-10-18, 14:05
Thanks Harsh that is helpful and it does work.
2012/10/12 Harsh J <[EMAIL PROTECTED]>
> The ${FOO} stuff can be replaced via JVM System Properties. I just > explained this on another thread (a few mails ago). > > So if your "library" JVM had a system property of > -DHOSTNAME=donkeykong.com then ${HOSTNAME} will be replaced by > donkeykong.com automatically. > > Likewise, even using Tool as the entry point of your app will let you > achieve the same via regular -D args. > > Hope this helps! > > On Fri, Oct 12, 2012 at 7:07 PM, Stephen Boesch <[EMAIL PROTECTED]> wrote: > > Hi, > > We are using a library with hdfs that uses custom properties inside > the > > *-site.xml files. Instead of (a) hard-coding or (b) writing a "sed" > script > > to update to the local hostnames on each deployed node, is there a > mechanism > > to use environment variables? > > > > <property> > > <name>custom.property</name> > > <value>${HOSTNAME}</value> > > </property> > > > > > > I have tried this and out of the box the string ${HOSTNAME} is used. > Anyone > > have recommendation/solution on this? > > > > thanks, > > > > stephen b > > > > -- > Harsh J >
|
|
All projects made searchable here are trademarks of the Apache Software Foundation.
Service operated by
Sematext