For example:
<job-tracker>${jobTracker}</job-tracker>
<name-node>${nameNode}</name-node>
<job-xml>${hiveSite}</job-xml>
<configuration>
<property>
<name>oozie.hive.defaults</name>
<value>${hiveDefault}</value>
</property>
<property>
<name>oozie.hive.log.level</name>
<value>${hiveLogLevel}</value>
</property>
</configuration>
On 3/21/13 3:37 PM, Paul Chavez wrote:
Have you tried putting a hive-site.xml in the deployment directory and then
referencing it in the <job-xml> element?
-----Original Message-----
From: Rohini Palaniswamy [mailto:[email protected]]
Sent: Thursday, March 21, 2013 12:27 PM
To: [email protected]; [email protected]
Subject: Re: HiveAction and hive-site.xml
+user mailing list.
Am I missing something? Can someone confirm that specifying all hive properties
in action conf is the only way to launch Hive Action of Oozie
3.3 with hive 0.9/0.10?
Regards,
Rohini
On Thu, Mar 21, 2013 at 10:07 AM, Rohini Palaniswamy < [email protected]>
wrote:
Hi,
I am trying out Hive action. I don't see any way currently in the
code to specify a hive-site.xml in workflow.xml. All the properties
have to be part of the action conf which are then written to a hive-site.xml.
hive-default.xml is out of question as Hive does not read it anymore.
Can't we let user specify a oozie-hive-site.xml file and include that
into hive-site.xml that is generated by oozie?
Regards,
Rohini
