Pre-process.xml already contains

<property>
    <name>oozie.action.sharelib.for.java</name>
    <value>hcatalog</value>
</property>

Oozie sharelib for hacatalog should contain all the required jars. So, if you 
make sure oozie sharelib is set-up correctly, this should work without any 
changes in falcon

Regards,
Shwetha

From: Mahak Mukhi <[email protected]<mailto:[email protected]>>
Reply-To: Mahak Mukhi <[email protected]<mailto:[email protected]>>
Date: Monday, 23 February 2015 10:07 pm
To: Shwetha Shivalingamurthy 
<[email protected]<mailto:[email protected]>>
Cc: Aaron Gresch <[email protected]<mailto:[email protected]>>, 
"[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: Configurational changes not getting relflected after build

Hi,

I tried updating the property but that doesn't work either; it's not getting 
reflected in the job workflow.
Does falcon store these template files somewhere on oozie server and could it 
be reading those obsolete files instead?

p.s. I am updating the pre-process.xml because the oozie jobs fail in that 
action with following exception: java.lang.NoClassDefFoundError: 
org/apache/hadoop/hive/conf/HiveConf
I had earlier rectified this error by updating table-export.xmla and 
table-import.xml, when those were the actions where the job failed.

Regards,
Mahak Mukhi


On Sunday, February 22, 2015 11:14 PM, Shwetha Shivalingamurthy 
<[email protected]<mailto:[email protected]>> 
wrote:


What are you trying to do? Why did you change pre-process.xml?

-Shwetha


On 21/02/15 2:13 am, "Mahak Mukhi" 
<[email protected]<mailto:[email protected]>> wrote:

>Hi,
>I made following changes in this file
>oozie/src/main/resources/action/pre-process.xml
>1. changed oozie:workflow:0.3 to oozie:workflow:0.4
> 2. added this property
>          <property>
>                <name>oozie.action.sharelib.for.hive</name>
>                <value>hcat_current,hive_current</value>
>            </property>
> But when I build it and submit feeds these changes aren't reflected in
>the oozie workflow. The job definition doesn't contain this newly added
>property neither is the new workflow version reflected. I looked up the
>jar(falcon-oozie-adaptor-0.7-SNAPSHOT.jar) in the deployed instance and
>the pre-process.xml in there shows the changes that I made, so I can be
>certain the deployment is valid. I even restarted the oozie server but to
>no success.
>
>Need help figuring out how this oozie workflow is not getting updated.
>
>Regards,Mahak Mukhi
>


Reply via email to