You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by Abhishek Bafna <ba...@gmail.com> on 2016/11/25 06:33:14 UTC
[VOTE] Release Oozie 4.3.0 (candidate 1)
Hi,
I have created a build for Oozie 4.3.0, candidate 1.
Keys to verify the signature of the release artifact are available at
http://www.apache.org/dist/oozie/KEYS <http://www.apache.org/dist/oozie/KEYS>
Please download, test, and try it out:
https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
<https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
The release, md5 signature, gpg signature, and rat report can all
be found at the above address.
Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
Thanks!
Abhishek Bafna
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by jaydeep vishwakarma <ja...@gmail.com>.
Verified the release candidate :
- Verified Signature
- Validated checksums
- LICENSE looks ok.
- Project build successfully without failing unit test cases
+1
Regards,
Jaydeep
On Thu, Dec 1, 2016 at 10:09 PM, Rohini Palaniswamy <rohini.aditya@gmail.com
> wrote:
> +1
>
> Verified rat report. Ran unit tests on the build and they were fine.
>
> Regards,
> Rohini
>
> On Wed, Nov 30, 2016 at 4:03 PM, Shwetha Shivalingamurthy <
> sshivalingamurthy@hortonworks.com> wrote:
>
> > +1
> >
> > Regards,
> > Shwetha
> >
> > > On Dec 1, 2016, at 4:43 AM, satish saley <sa...@gmail.com>
> > wrote:
> > >
> > > Hello,
> > >
> > > Thank you for build Abhishek.
> > >
> > > - ./bin/mkdistro.sh -Puber
> > > Succeeded
> > > - Launched Oozie server on my laptop
> > > - Successfully ran sample jobs
> > >
> > > +1
> > >
> > >
> > > On Wed, Nov 30, 2016 at 5:31 AM, Attila Sasvari <asasvari@cloudera.com
> >
> > > wrote:
> > >
> > >> Hi
> > >>
> > >> * Built distro with
> > >> bin/mkdistro.sh -DskipTests=true -Puber (using java version
> > "1.7.0_80")
> > >> * Installed Oozie sharelib
> > >> * Started Oozie server
> > >> * Put examples to HDFS
> > >> * Executed a workflow locally on a pseudo Hadoop cluster without HTTPS
> > and
> > >> without Kerberos
> > >> bin/oozie job -oozie http://localhost:11000/oozie -config
> > >> examples/apps/java-main/job.properties -run
> > >> -DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032
> > >> -Dlog4j.configuration=./conf/oozie-log4j.properties
> > >>
> > >> => Worfklow succeeded.
> > >>
> > >>
> > >>
> > >> On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <bafna.iitr@gmail.com
> >
> > >> wrote:
> > >>
> > >>> Hi,
> > >>>
> > >>> I have created a build for Oozie 4.3.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:
> > >>>
> > >>> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
> > >>> <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
> > >>>
> > >>> The release, md5 signature, gpg signature, and rat report can all
> > >>> be found at the above address.
> > >>>
> > >>> Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
> > >>>
> > >>> Thanks!
> > >>> Abhishek Bafna
> > >>>
> > >>>
> > >>
> >
>
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by Rohini Palaniswamy <ro...@gmail.com>.
+1
Verified rat report. Ran unit tests on the build and they were fine.
Regards,
Rohini
On Wed, Nov 30, 2016 at 4:03 PM, Shwetha Shivalingamurthy <
sshivalingamurthy@hortonworks.com> wrote:
> +1
>
> Regards,
> Shwetha
>
> > On Dec 1, 2016, at 4:43 AM, satish saley <sa...@gmail.com>
> wrote:
> >
> > Hello,
> >
> > Thank you for build Abhishek.
> >
> > - ./bin/mkdistro.sh -Puber
> > Succeeded
> > - Launched Oozie server on my laptop
> > - Successfully ran sample jobs
> >
> > +1
> >
> >
> > On Wed, Nov 30, 2016 at 5:31 AM, Attila Sasvari <as...@cloudera.com>
> > wrote:
> >
> >> Hi
> >>
> >> * Built distro with
> >> bin/mkdistro.sh -DskipTests=true -Puber (using java version
> "1.7.0_80")
> >> * Installed Oozie sharelib
> >> * Started Oozie server
> >> * Put examples to HDFS
> >> * Executed a workflow locally on a pseudo Hadoop cluster without HTTPS
> and
> >> without Kerberos
> >> bin/oozie job -oozie http://localhost:11000/oozie -config
> >> examples/apps/java-main/job.properties -run
> >> -DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032
> >> -Dlog4j.configuration=./conf/oozie-log4j.properties
> >>
> >> => Worfklow succeeded.
> >>
> >>
> >>
> >> On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <ba...@gmail.com>
> >> wrote:
> >>
> >>> Hi,
> >>>
> >>> I have created a build for Oozie 4.3.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:
> >>>
> >>> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
> >>> <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
> >>>
> >>> The release, md5 signature, gpg signature, and rat report can all
> >>> be found at the above address.
> >>>
> >>> Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
> >>>
> >>> Thanks!
> >>> Abhishek Bafna
> >>>
> >>>
> >>
>
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by Shwetha Shivalingamurthy <ss...@hortonworks.com>.
+1
Regards,
Shwetha
> On Dec 1, 2016, at 4:43 AM, satish saley <sa...@gmail.com> wrote:
>
> Hello,
>
> Thank you for build Abhishek.
>
> - ./bin/mkdistro.sh -Puber
> Succeeded
> - Launched Oozie server on my laptop
> - Successfully ran sample jobs
>
> +1
>
>
> On Wed, Nov 30, 2016 at 5:31 AM, Attila Sasvari <as...@cloudera.com>
> wrote:
>
>> Hi
>>
>> * Built distro with
>> bin/mkdistro.sh -DskipTests=true -Puber (using java version "1.7.0_80")
>> * Installed Oozie sharelib
>> * Started Oozie server
>> * Put examples to HDFS
>> * Executed a workflow locally on a pseudo Hadoop cluster without HTTPS and
>> without Kerberos
>> bin/oozie job -oozie http://localhost:11000/oozie -config
>> examples/apps/java-main/job.properties -run
>> -DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032
>> -Dlog4j.configuration=./conf/oozie-log4j.properties
>>
>> => Worfklow succeeded.
>>
>>
>>
>> On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <ba...@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> I have created a build for Oozie 4.3.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:
>>>
>>> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
>>> <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
>>>
>>> The release, md5 signature, gpg signature, and rat report can all
>>> be found at the above address.
>>>
>>> Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
>>>
>>> Thanks!
>>> Abhishek Bafna
>>>
>>>
>>
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by satish saley <sa...@gmail.com>.
Hello,
Thank you for build Abhishek.
- ./bin/mkdistro.sh -Puber
Succeeded
- Launched Oozie server on my laptop
- Successfully ran sample jobs
+1
On Wed, Nov 30, 2016 at 5:31 AM, Attila Sasvari <as...@cloudera.com>
wrote:
> Hi
>
> * Built distro with
> bin/mkdistro.sh -DskipTests=true -Puber (using java version "1.7.0_80")
> * Installed Oozie sharelib
> * Started Oozie server
> * Put examples to HDFS
> * Executed a workflow locally on a pseudo Hadoop cluster without HTTPS and
> without Kerberos
> bin/oozie job -oozie http://localhost:11000/oozie -config
> examples/apps/java-main/job.properties -run
> -DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032
> -Dlog4j.configuration=./conf/oozie-log4j.properties
>
> => Worfklow succeeded.
>
>
>
> On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <ba...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I have created a build for Oozie 4.3.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:
> >
> > https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
> > <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
> >
> > The release, md5 signature, gpg signature, and rat report can all
> > be found at the above address.
> >
> > Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
> >
> > Thanks!
> > Abhishek Bafna
> >
> >
>
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by Attila Sasvari <as...@cloudera.com>.
Hi
* Built distro with
bin/mkdistro.sh -DskipTests=true -Puber (using java version "1.7.0_80")
* Installed Oozie sharelib
* Started Oozie server
* Put examples to HDFS
* Executed a workflow locally on a pseudo Hadoop cluster without HTTPS and
without Kerberos
bin/oozie job -oozie http://localhost:11000/oozie -config
examples/apps/java-main/job.properties -run
-DnameNode=hdfs://localhost:9000 -DjobTracker=localhost:8032
-Dlog4j.configuration=./conf/oozie-log4j.properties
=> Worfklow succeeded.
On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <ba...@gmail.com>
wrote:
> Hi,
>
> I have created a build for Oozie 4.3.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:
>
> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
> <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
> Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
>
> Thanks!
> Abhishek Bafna
>
>
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by Robert Kanter <rk...@cloudera.com>.
+1
+ I'm fine with ignoring the pyspark test issue for now
+ Verified md5
+ Verified signature with gpg
+ RAT report looks good
+ Ran some of the examples against Hadoop 2.4.0, clicked around the UI, and
looked at the docs after compiling with the hadoop-2 and uber profiles (mvn
clean package assembly:single -DskipTests -Phadoop-2 -Puber -DgenerateDocs)
- The README.txt file has some out of date stuff in it, but it's been that
way for a long time so I've just filed OOZIE-2747 to fix that for the next
release; no reason to block the release just for that.
- Robert
On Mon, Nov 28, 2016 at 1:34 PM, Peter Cseh <ge...@cloudera.com> wrote:
> Hi,
>
> Thank you for building the RC Abhishek!
> I've managed to download the rc - md5, signatures are looking good.
> It took a couple tries, but I managed to build the distro with all tests
> passing:
>
> >> [229] 15:32 : oozie-4.3.0 :: ./bin/mkdistro.sh -Puber
> .....
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------
> ------------
> [INFO] Total time: 01:13 h
> [INFO] Finished at: 2016-11-28T15:32:29+01:00
> [INFO] Final Memory: 155M/1903M
> [INFO] ------------------------------------------------------------
> ------------
>
> Oozie distro created, DATE[2016.11.28-13:19:16GMT] VC-REV[unavailable],
> available at [/Users/gezapeti/Downloads/oozie-4.3.0-rc1/oozie-4.3.0/
> distro/target]
>
> I've checked that the rc compiles with spark-2.
> The bad news is that the Pyspark test is failing:
> >> [248] 21:51 : oozie-4.3.0 :: mvn test -pl
> org.apache.oozie:oozie-sharelib-spark -am -Pspark-2 -Dtest=*park*
> Failed tests: testPyspark(org.apache.oozie.action.hadoop.TestPyspark):
> expected:<[SUCCEED]ED> but was:<[FAILED/KILL]ED>
>
> I'm pretty sure that the test is broken because of the way we've added the
> test back then:
> https://github.com/apache/oozie/commit/b0ebf58e86f26f01571f558bf3b04d
> 1788b8380f
> We've pushed in the zip files needed for 1.6.1 because it's not trivial to
> the these files from anywhere else.
> I've tried to make it work by copying the new zip files over but I couldn't
> make it work.
> If anyone can make it work I think we could ignore this test failure and
> add a known issue for the release notes.
>
> The rc is compiling with hadoop-1 profile active, but I haven't ran the
> tests for that case.
>
> I'll try to make some time to submit the examples on a cluster this week.
>
> Best regards,
> gp
>
>
> On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <ba...@gmail.com>
> wrote:
>
> > Hi,
> >
> > I have created a build for Oozie 4.3.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:
> >
> > https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
> > <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
> >
> > The release, md5 signature, gpg signature, and rat report can all
> > be found at the above address.
> >
> > Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
> >
> > Thanks!
> > Abhishek Bafna
> >
> >
>
>
> --
> Peter Cseh
> Software Engineer
> <http://www.cloudera.com>
>
Re: [VOTE] Release Oozie 4.3.0 (candidate 1)
Posted by Peter Cseh <ge...@cloudera.com>.
Hi,
Thank you for building the RC Abhishek!
I've managed to download the rc - md5, signatures are looking good.
It took a couple tries, but I managed to build the distro with all tests
passing:
>> [229] 15:32 : oozie-4.3.0 :: ./bin/mkdistro.sh -Puber
.....
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------
------------
[INFO] Total time: 01:13 h
[INFO] Finished at: 2016-11-28T15:32:29+01:00
[INFO] Final Memory: 155M/1903M
[INFO] ------------------------------------------------------------
------------
Oozie distro created, DATE[2016.11.28-13:19:16GMT] VC-REV[unavailable],
available at [/Users/gezapeti/Downloads/oozie-4.3.0-rc1/oozie-4.3.0/
distro/target]
I've checked that the rc compiles with spark-2.
The bad news is that the Pyspark test is failing:
>> [248] 21:51 : oozie-4.3.0 :: mvn test -pl
org.apache.oozie:oozie-sharelib-spark -am -Pspark-2 -Dtest=*park*
Failed tests: testPyspark(org.apache.oozie.action.hadoop.TestPyspark):
expected:<[SUCCEED]ED> but was:<[FAILED/KILL]ED>
I'm pretty sure that the test is broken because of the way we've added the
test back then:
https://github.com/apache/oozie/commit/b0ebf58e86f26f01571f558bf3b04d1788b8380f
We've pushed in the zip files needed for 1.6.1 because it's not trivial to
the these files from anywhere else.
I've tried to make it work by copying the new zip files over but I couldn't
make it work.
If anyone can make it work I think we could ignore this test failure and
add a known issue for the release notes.
The rc is compiling with hadoop-1 profile active, but I haven't ran the
tests for that case.
I'll try to make some time to submit the examples on a cluster this week.
Best regards,
gp
On Fri, Nov 25, 2016 at 7:33 AM, Abhishek Bafna <ba...@gmail.com>
wrote:
> Hi,
>
> I have created a build for Oozie 4.3.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:
>
> https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc1/
> <https://dist.apache.org/repos/dist/dev/oozie/oozie-4.3.0-rc0/>
>
> The release, md5 signature, gpg signature, and rat report can all
> be found at the above address.
>
> Vote closes on [Thursday Dec. 01 11:00:00 IST 2016].
>
> Thanks!
> Abhishek Bafna
>
>
--
Peter Cseh
Software Engineer
<http://www.cloudera.com>