[
https://issues.apache.org/jira/browse/OOZIE-2610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15385588#comment-15385588
]
abhishek bafna commented on OOZIE-2610:
---------------------------------------
When does this exactly fails? Are you doing start/stop from ambari or manually
and expecting variable to be resolved from {{core-site.xml}}?
> oozie does not do variable expansion of property in core-site
> -------------------------------------------------------------
>
> Key: OOZIE-2610
> URL: https://issues.apache.org/jira/browse/OOZIE-2610
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: 4.2.0
> Reporter: Dilli Dorai Minnal Arumugam
>
> We are using value of ${fs.defaultFS.native} for property in core-site.xml
> Relevant snippet in /etc/hadoop/conf/core-site.xml looks like the following:
> <property>
> <name>fs.defaultFS</name>
> <value>${fs.defaultFS.native}</value>
> </property>
> <property>
> <name>fs.defaultFS.native</name>
> <value>hdfs://c6401.ambari.apache.org:8020</value>
> </property>
> With these settings in /etc/hadoop/conf/core-site.xml, all the services
> except oozie start fine.
> oozie fails to start with the following message
> /usr/hdp/current/oozie-server/bin/oozie-setup.sh sharelib create -fs
> ${fs.defaultFS.native} -locallib /usr/hdp/current/oozie-server/share'
> returned 1. -bash: ${fs.defaultFS.native}: bad substitution
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
