The hadoop-2, hadoop-3, and hadoop-0.23 profiles set the pig classifier and sqoop classifier. As long as the user uses the same hadoop profile as what they are running against, the sharelib will have the right pig and sqoop jars. e.g. If deploying with Hadoop 2, they should use the hadoop-2 profile. If they deploy with hadoop-1 and use the hadoop-2 profile, the sharelib will be wrong, but that's expected.
On Tue, Nov 18, 2014 at 1:23 PM, bowen zhang < [email protected]> wrote: > I guess we might need to document the fact for pig to run with hadoop-2, > you need "-Dpig.classifier=2" as a maven command line option > > From: Rohini Palaniswamy <[email protected]> > To: "[email protected]" <[email protected]> > Cc: bowen zhang <[email protected]> > Sent: Tuesday, November 18, 2014 3:27 AM > Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1) > > +1 > > > > On Tue, Nov 18, 2014 at 2:36 AM, Ryota Egashira < > [email protected]> wrote: > > > +1 > > -Built release artifact successfully > > -ran couple of example jobs on single-node setting, which succeeded. > > > > Ryota > > > > On 11/17/14, 5:10 PM, "Robert Kanter" <[email protected]> wrote: > > > > >+1 > > > > > >- downloaded release artifacts > > >- built with Hadoop 1.1.1 (though ran against Hadoop 1.2.0) and ran a > few > > >of the examples. > > >- built with Hadoop 2.3.0 (though ran against Hadoop some > 2.7.0-SNAPSHOT) > > >and ran a few of the examples. There's something wrong with my Hadoop 2 > > >setup, but as far as I could tell, Oozie was working properly. > > > > > >- One thing: the release-log says that 4.1 is unrelated. That should be > > >removed. While you're at it, please also fix that for 4.0.1, I > apparently > > >forgot to do that too :) > > > > > >- (And the key issue that was already mentioned should be fixed) > > > > > > > > >On Mon, Nov 17, 2014 at 11:18 AM, Mohammad Islam > > ><[email protected] > > >> wrote: > > > > > >> Sorry Bowen for the delay.I'm looking into this , I never tried that. > > >> Regards,Mohammad > > >> > > >> On Monday, November 17, 2014 9:58 AM, bowen zhang > > >> <[email protected]> wrote: > > >> > > >> > > >> Hi Mohammad,I think the KEY issue is the reason Mona has problem > > >>signing > > >> the page since I cannot commit my key to the repo. Can you resolve > this > > >> ASAP?Thanks,Bowen > > >> > > >> From: Mona Chitnis <[email protected]> > > >> To: "[email protected]" <[email protected]>; bowen zhang < > > >> [email protected]> > > >> Sent: Monday, November 17, 2014 9:15 AM > > >> Subject: Re: VOTE Release Oozie 4.1.0 (candidate 1) > > >> > > >> Downloaded the tarball, built and installed Oozie (-DskipTests) and > ran > > >>an > > >> example M-R Oozie job against my Hadoop 2.4 cluster. +1 for that. > > >> Was unable to verify the md5 and gpg signatures. I dont find the key > > >>used > > >> for signing the page in the list of public keys on the KEYS page. > Please > > >> let me know if I'm missing the right procedure. > > >> Regards, Mona Chitnis > > >> > > >> > > >> > > >> > > >> On Monday, November 17, 2014 8:08 AM, Shwetha GS < > > >> [email protected]> wrote: > > >> > > >> > > >> +1 > > >> > > >> On Fri, Nov 14, 2014 at 6:49 AM, bowen zhang < > > >> [email protected]> wrote: > > >> > > >> > Hi, > > >> > > > >> > I have created a build for Oozie 4.1.0, candidate 1. > > >> > > > >> > Keys to verify the signature of the release artifact are available > at > > >> > > > >> > http://www.apache.org/dist/oozie/KEYS > > >> > > > >> > Please download, test, and try it out: > > >> > > > >> > http://people.apache.org/~bzhang/oozie-4.1.0-rc1 > > >> > > > >> > The release, md5 signature, gpg signature, and rat report can all > > >> > be found at the above address. > > >> > > > >> > Vote closes on Monday EOD, the 17th. > > >> > > > >> > Bowen > > >> > > > >> > > >> -- > > >> _____________________________________________________________ > > >> The information contained in this communication is intended solely for > > >>the > > >> use of the individual or entity to whom it is addressed and others > > >> authorized to receive it. It may contain confidential or legally > > >>privileged > > >> information. If you are not the intended recipient you are hereby > > >>notified > > >> that any disclosure, copying, distribution or taking any action in > > >>reliance > > >> on the contents of this information is strictly prohibited and may be > > >> unlawful. If you have received this communication in error, please > > >>notify > > >> us immediately by responding to this email and then delete it from > your > > >> system. The firm is neither liable for the proper and complete > > >>transmission > > >> of the information contained in this communication nor for any delay > in > > >>its > > >> receipt. > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > >> > > > > > > > >
