That would be ideal. With MRUnit for example both builds are in the repo and you use <classifier>hadoop2</classifier> to get the right one.
From: Garrett Wu
Sent: 16 Jul 2012 16:56:54 GMT
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: avro 1.7.0 with CDH4
What is the correct solution for making avro-1.7 work with both Hadoop 1
(CDH3) and Hadoop 2 (CDH4)? Should we add build profiles for each so we can
release two separate avro-mapred jars?
On Thu, Jul 5, 2012 at 5:12 AM, Jacob Metcalf <[EMAIL PROTECTED]>wrote:
> Avro 17 is compiled against Hadoop 1 i.e. CDH3.
> I have it running aginst CDH4 but I had to patch and recompile Avro, then
> replace the Avro 153 in the Hadoop lib directory with 17. I have attached
> my patch against JIRA AVRO-1103 for consideration.
> -----Original Message-----
> From: Alan Miller
> Sent: 5 Jul 2012 11:03:06 GMT
> To: [EMAIL PROTECTED]
> Subject: Re: avro 1.7.0 with CDH4
> I noticed that CDH4 has avro-1.5.4.jar in hadoop/lib so I modified my job
> 1. avro-1.7.0.jar and avro-tools-1.7.0.jar is contained within my jar
> in ./lib/
> (note: I submit my job via hadoop jar myjar.jar myDriver <myopts ....>)
> 2. I have also set: mapreduce.task.classpath.first=true (in
> to ensure the 1.7.0 jars from the lib dir in my.jar are used first
> (before avro-1.5.4).
> But I still get the same error.
> Any ideas?
> View this message in context:
> Sent from the Avro - Users mailing list archive at Nabble.com.