Hi All,

We still have only one vote (+1), so I extend the voting period again.
Please cast your vote till Dec 1st.

Best,
Sala

On Mon, Nov 18, 2019 at 10:41 AM Andras Salamon <[email protected]>
wrote:

> Hi All,
>
> We only have one vote so far (+1), so I extend the voting till Nov 24th.
> Please test 5.2.0 RC0 if you have time.
>
> Best,
> Sala
>
> On Thu, Nov 14, 2019 at 3:32 PM Peter Cseh <[email protected]>
> wrote:
>
>> Andras, thanks for building the RC and the summary!
>> I don't think that the Java 11 issues are a problem, especially if it
>> works
>> when compiling with a different Hadoop.
>>
>> The checksums and signatures are good.
>> I've used Jdk8u212 on my mac to build the distro.
>> Distro creation succeeded with all tests passing:
>>  ./bin/mkdistro.sh  -Dtest.timeout=7200 -Doozie.test.waitfor.ratio=3
>> -Dsurefire.rerunFailingTestsCount=3
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Reactor Summary for Apache Oozie Main 5.2.0:
>> [INFO]
>> [INFO] Apache Oozie Main .................................. SUCCESS [
>>  1.538 s]
>> [INFO] Apache Oozie Fluent Job ............................ SUCCESS [
>>  0.082 s]
>> [INFO] Apache Oozie Fluent Job API ........................ SUCCESS [
>> 13.131 s]
>> [INFO] Apache Oozie Client ................................ SUCCESS [
>> 10.897 s]
>> [INFO] Apache Oozie Share Lib Oozie ....................... SUCCESS [
>>  6.554 s]
>> [INFO] Apache Oozie Share Lib HCatalog .................... SUCCESS [
>>  3.479 s]
>> [INFO] Apache Oozie Share Lib Distcp ...................... SUCCESS [
>>  0.388 s]
>> [INFO] Apache Oozie Core .................................. SUCCESS [
>>  01:27 h]
>> [INFO] Apache Oozie Share Lib Streaming ................... SUCCESS [12:50
>> min]
>> [INFO] Apache Oozie Share Lib Pig ......................... SUCCESS [05:38
>> min]
>> [INFO] Apache Oozie Share Lib Git ......................... SUCCESS [
>> 59.980 s]
>> [INFO] Apache Oozie Share Lib Hive ........................ SUCCESS [02:41
>> min]
>> [INFO] Apache Oozie Share Lib Hive 2 ...................... SUCCESS [02:20
>> min]
>> [INFO] Apache Oozie Share Lib Sqoop ....................... SUCCESS [05:14
>> min]
>> [INFO] Apache Oozie Examples .............................. SUCCESS [
>> 33.237 s]
>> [INFO] Apache Oozie Share Lib Spark ....................... SUCCESS [02:10
>> min]
>> [INFO] Apache Oozie Share Lib ............................. SUCCESS [
>> 16.819 s]
>> [INFO] Apache Oozie Docs .................................. SUCCESS [
>>  0.388 s]
>> [INFO] Apache Oozie WebApp ................................ SUCCESS [
>>  4.631 s]
>> [INFO] Apache Oozie Tools ................................. SUCCESS [
>> 47.751 s]
>> [INFO] Apache Oozie MiniOozie ............................. SUCCESS [
>> 56.070 s]
>> [INFO] Apache Oozie Fluent Job Client ..................... SUCCESS [
>> 48.696 s]
>> [INFO] Apache Oozie Server ................................ SUCCESS [
>>  5.554 s]
>> [INFO] Apache Oozie Distro ................................ SUCCESS [
>> 39.502 s]
>> [INFO] Apache Oozie ZooKeeper Security Tests .............. SUCCESS [
>> 47.454 s]
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time:  02:05 h
>> [INFO] Finished at: 2019-11-14T14:46:01+01:00
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> Oozie distro created, DATE[2019.11.14-11:40:54GMT] VC-REV[unavailable],
>> available at [/Users/gezapeti/tmp/oozie-5.2.0/distro/target]
>>
>> I've also set up a local Hadoop (2.6.0) and managed to submit some jobs. I
>> don't have the time to run a kerberized test unfortunately.
>>
>> +1 from my side.
>>
>>
>>
>>
>> On Thu, Nov 14, 2019 at 11:27 AM Andras Salamon
>> <[email protected]> wrote:
>>
>> > Hi,
>> >
>> > I have tested the Java 10/11 compilation and found the following:
>> >
>> > Oozie cannot be compiled if we use Java 10/11 + Linux + Hadoop 2.6.x
>> >
>> > It's possible to compile using Java 11 + Mac + Hadoop 2.6.x or Java 11 +
>> > Linux + Hadoop 2.7.x
>> >
>> > I have opened a jira about this:
>> > https://issues.apache.org/jira/browse/OOZIE-3558
>> >
>> > Best,
>> > Sala
>> >
>> > On Mon, Nov 11, 2019 at 8:44 PM Attila Sasvári <[email protected]>
>> > wrote:
>> >
>> > > I failed to build Oozie 5.2.0 rc0 with OpenJDK 10 and OpenJDK 8.
>> > >
>> > > # Oozie 5.2.0 rc0 with Java 10 :
>> > > - downloaded
>> > >
>> https://people.apache.org/~asalamon74/oozie-5.2.0-rc0/oozie-5.2.0.tar.gz
>> > > - extracted it to oozie-5.2.0
>> > > - based on the public OpenJDK 10 Docker image (
>> > > https://hub.docker.com/_/openjdk), created the following Dockerfile
>> to
>> > > make
>> > > the Oozie distro:
>> > >
>> > > FROM openjdk:10
>> > > RUN apt update -y
>> > > RUN apt install -y maven
>> > > COPY oozie-5.2.0 /usr/src/oozie
>> > > WORKDIR /usr/src/oozie
>> > > RUN bin/mkdistro.sh -DskipTests
>> > >
>> > > - docker build -f Dockerfile . failed with
>> > >
>> > > [ERROR] Failed to execute goal on project oozie-fluent-job-api: Could
>> not
>> > > resolve dependencies for project
>> > > org.apache.oozie:oozie-fluent-job-api:jar:5.2.0: Could not find
>> artifact
>> > > jdk.tools:jdk.tools:jar:1.6 at specified path
>> > > /usr/lib/jvm/java-10-openjdk-amd64/../lib/tools.jar -> [Help 1]
>> > >
>> > > when it tried to build the Fluent Job API.
>> > >
>> > > - Fluent Job API's jaxb dependency seems to rely on the existence of
>> > > tools.jar. However, JEP-220 (https://openjdk.java.net/jeps/220)
>> removed
>> > > tools.jar and it affects JDK 9+ environments.
>> > >
>> > > # Oozie 5.2.0 rc0 with Java 8, using the OpenJDK 8 base Docker image:
>> > > - Dockerfile
>> > > FROM openjdk:8
>> > > RUN apt update -y
>> > > RUN apt install -y maven
>> > > COPY oozie-5.2.0 /usr/src/oozie
>> > > WORKDIR /usr/src/oozie
>> > > RUN bin/mkdistro.sh -DskipTests
>> > >
>> > > Building Apache Oozie WebApp failed with a different error:
>> > >
>> > > [ERROR] Failed to execute goal
>> > > org.apache.maven.plugins:maven-dependency-plugin:3.0.2:copy
>> > (copy-sharelib)
>> > > on project oozie-webapp: Unable to find/resolve artifact.
>> > > com.google.inject.ProvisionException: Unable to provision, see the
>> > > following errors:
>> > > [ERROR]
>> > > [ERROR] 1) Error injecting: private org.eclipse.aether.spi.log.Logger
>> > >
>> org.apache.maven.repository.internal.DefaultVersionRangeResolver.logger
>> > > [ERROR] while locating
>> > > org.apache.maven.repository.internal.DefaultVersionRangeResolver
>> > >
>> > > Has anyone else experienced similar build failures?
>> > >
>> > > Regards,
>> > > - Attila
>> > >
>> > > On Sun, Nov 10, 2019 at 10:59 PM Attila Sasvári <[email protected]
>> >
>> > > wrote:
>> > > >
>> > > > Hi Sala,
>> > > >
>> > > > Many thanks for driving the release.
>> > > >
>> > > > Can you please outline main changes and new features of Oozie 5.2?
>> > > >
>> > > > Best,
>> > > > - Attila
>> > > >
>> > > > On Fri, Nov 8, 2019 at 11:15 AM Andras Salamon
>> > > <[email protected]> wrote:
>> > > >>
>> > > >> Hi,
>> > > >>
>> > > >> I have created a build for Oozie 5.2.0, candidate 0.
>> > > >>
>> > > >> Keys to verify the signature of the release artifact are available
>> at
>> > > >>
>> > > >>   https://www.apache.org/dist/oozie/KEYS
>> > > >>
>> > > >> Please download, test, and try it out:
>> > > >>
>> > > >>   https://people.apache.org/~asalamon74/oozie-5.2.0-rc0/
>> > > >>
>> > > >> The release, sha512 signature, gpg signature, and rat report can
>> all
>> > > >> be found at the above address.
>> > > >>
>> > > >> Vote closes on Nov 17th.
>> > > >>
>> > > >> Thanks,
>> > > >> Sala
>> > >
>> >
>>
>>
>> --
>> *Peter Cseh* | Software Engineer, Cloudera Search
>> cloudera.com <https://www.cloudera.com>
>> [image: Cloudera] <https://www.cloudera.com/>
>> [image: Cloudera on Twitter] <https://twitter.com/cloudera> [image:
>> Cloudera on Facebook] <https://www.facebook.com/cloudera> [image:
>> Cloudera
>> on LinkedIn] <https://www.linkedin.com/company/cloudera>
>> <https://www.cloudera.com/>
>> ------------------------------
>>
>

Reply via email to