Thanks Attila for taking the time to test the RC2! To answer your observations:
1. OOZIE-3378 <https://issues.apache.org/jira/browse/OOZIE-3378> is fixed and scheduled to ship as part of 5.2.0 2. opened up OOZIE-3402 <https://issues.apache.org/jira/browse/OOZIE-3402> to track duplicate error code inside error message 3. opened up OOZIE-3403 <https://issues.apache.org/jira/browse/OOZIE-3403> to track that OozieCLI creates workflow.xml inside /tmp on the client host. Since this information is also available via normal OozieCLI calls, I'd consider it as a minor Regards, Andras On Wed, Dec 12, 2018 at 11:53 PM Attila Sasvari <asasv...@cloudera.com.invalid> wrote: > Hi there, > > +1 (but please see my observations below) > > Here is what I did: > - built Oozie with Hadoop version 2.7.5, installed Oozie sharelib, started > the server, > - executed example workflows using a single node, pseudo Hadoop cluster, > - clicked through the Oozie Web UI to validate basic functionality (checked > job statuses, logs, DAG), > - created a demo workflow using the Oozie Fluent job API, validated and > submitted via Oozie CLI, > - verified the issues reported on RC 1 are now fixed. > > Some observations: > - I was hit by OOZIE-3378. As I understand that it will be included in the > next minor release. > - Some of the error messages contain error code twice. For example: "Error: > E0307 : E0307: Runtime error [App directory > [hdfs://localhost:9000/user/root/examples/apps/subwf] does not exist and > app definition cannot be created because of missing > config value [oozie.jobs.api.generated.xml]]" > - I noticed that when we validate workflows generated via the fluent job > API using the Oozie CLI with "-validatejar" and "--verbose" options, > temporary XML files are created in a world readable directory (/tmp) on the > client side. It is not a good thing, but I am not sure if it qualifies as a > blocker. What do you think? If we consider it a blocker, then OOZIE-3378 > could be also included in the next RC. > > - Attila > > > On Wed, Dec 12, 2018 at 5:15 PM Andras Salamon > <asala...@cloudera.com.invalid> wrote: > > > Thanks Peter, > > > > 1) I've opened an upstream jira: > > https://issues.apache.org/jira/browse/OOZIE-3401 > > > > Sala > > > > On Wed, Dec 12, 2018 at 5:05 PM Andras Piros > > <andras.pi...@cloudera.com.invalid> wrote: > > > > > 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 > > <pbac...@cloudera.com.invalid > > > > > > > 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 <and...@apache.org> > > 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 <and...@apache.org> > > 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 > > > > > > > > > > > > > > > > > > > > > > > -- > -- > Attila Sasvari > Software Engineer > <http://www.cloudera.com/> >
