Right, source release shouldn't matter because you just activate whichever Hadoop profile you want when building.
I think these are the only things that are incompatible: 1. DistCp sharelib: contains different versions of the jar depending on the Hadoop profile activated 2. Streaming sharelib: same as DistCp sharelib 3. Some of the other actions have different jars or classifiers etc depending on the Hadoop profile activated 4. The oozie-hadoop-utils jar I added in OOZIE-1722: like the other hadooplibs, it has different implementations for each Hadoop version 5. The hadoop-auth jars The first four of those end up in the sharelib and are used only by the launcher job, though I believe they are also included in the webapp module, so you can't simply ship two versions of the sharelib. Though, that's actually what we do in CDH.... Does anyone remember why we include these in webapp module? hadoop-auth is actually used by the Oozie server. So, I'm thinking we do need separate 1.x and 2.x builds. On Wed, Jun 11, 2014 at 5:53 PM, Mohammad Islam <misla...@yahoo.com.invalid> wrote: > Thanks Mona for bringing it. > > At first, do we need to build for hadoop 1.x and hadoop 2.x? why? > > Btw, for source release, it is not applicable. right? > > Regards, > Mohammad > > > > On Wednesday, June 11, 2014 5:37 PM, Mona Chitnis <m...@apache.org> wrote: > > > > Hi, > > Following up from the meetup discussion about Oozie not being bytecode > compatible now across Hadoop-1.x and 2.x due to recent changes. Let us > properly define what are the changes that are breaking this and what is the > plan going forth (2 releases each time or not) > > > Mona Chitnis > Yahoo! >
