Thank you, Micah! Adding this to the configuration section of my java
action solved the problem:
<property>
<name>oozie.launcher.mapreduce.user.classpath.first</name>
<value>true</value>
</property>
Best, Aaron
On 12/16/15, 5:48 PM, "Micah Whitacre" <[email protected]> wrote:
>There was a similar discussion about this in the archives:
>https://mail-archives.apache.org/mod_mbox/oozie-user/201308.mbox/%3C9F2E10
>[email protected]%3E
>
>You might try the settings mentioned there.
>
>On Wed, Dec 16, 2015 at 3:15 PM, Aaron.Dossett <[email protected]>
>wrote:
>
>> Hi,
>>
>> I have a java action and would like to ensure that the jars I provide
>>(via
>> the lib/ directory) have the highest precedence in the class path my
>>java
>> action executes with. Is that possible?
>>
>> The very specific problem I'm dealing with is that when running a java
>> action in oozie, an old version of jackson-core is getting picked up
>>here:
>>
>>
>>
>>jar:file:/hadoop/yarn/local/filecache/22/mapreduce.tar.gz/hadoop/share/ha
>>doop/common/lib/jackson-core-2.2.3.jar!/com/fasterxml/jackson/core/JsonFa
>>ctory.class
>>
>> My own jar files have a more recent version of jackson-core, but the
>>above
>> location has class path priority. I am running on an HDP 2.2.4 cluster.
>>
>> Thanks! -Aaron
>>
