Thanks Peter,

2) resembles *PIG-5253 <http://PIG-5253>* which is in progress. Oozie's
Hadoop 3 support efforts are tracked under *OOZIE-2973
<https://issues.apache.org/jira/browse/OOZIE-2973>*.

Regards,

Andras

On Wed, Dec 12, 2018 at 3:30 PM Peter Bacsko <[email protected]>
wrote:

> +1 (binding, conditional)
>
> - verified hash
> - verified signature
> - built distro & ran all tests
> - created Hadoop pseudo dist cluster, executed sample Java workflow
>
> Things I observed:
> 1. TestPyspark constantly fails locally, but passes in Jenkins. Please
> investigate that it's a test failure and create a JIRA to track it.
> 2. Not possible to build distro if -Dhadoop.version is set to 2.9.2. Please
> confirm that it's not Oozie's fault.
>
> Peter
>
>
> On Mon, Dec 10, 2018 at 1:50 PM Andras Piros <[email protected]> wrote:
>
> > Hi,
> >
> > as no votes were cast so far extending the deadline by one week, until
> > Friday, December 14, 2018 at 12:00am PDT.
> >
> > Please check the new RC and cast your vote accordingly.
> >
> > Thanks,
> >
> > Andras
> >
> >
> > On Mon, Dec 3, 2018 at 2:29 PM Andras Piros <[email protected]> wrote:
> >
> > > Hi there,
> > >
> > > I have created a build for Oozie 5.1.0, release candidate 2.
> > >
> > > This release introduces following major changes and fixes:
> > > - Fluent Job API
> > > - Git action
> > > - reduced heap waste
> > > - switched documentation from TWiki to Markdown
> > > - callable queue improvements
> > > - Spark action fixes
> > > - SLA improvements
> > > - third party dependency revamp
> > > - fixed CVE-2018-11799
> > >
> > > 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/~andras/oozie-5.1.0-rc2/
> > >
> > > The release candidate, sha512 signature, gpg signature, and rat report
> > can
> > > all be found
> > > at the above address.
> > >
> > > The vote is open until Friday, December 7, 2018 at 12:00am PDT.
> > >
> > > Thanks,
> > >
> > > Andras Piros
> > >
> >
>

Reply via email to