[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (94 issues) Subscriber: ooziedaily Key Summary OOZIE-3561 Forkjoin validation is slow when there are many actions in chain https://issues.apache.org/jira/browse/OOZIE-3561 OOZIE-3560 IDEA shows have some error in index.jsp https://issues.apache.org/jira/browse/OOZIE-3560 OOZIE-3557 [build] Update required minimum maven version https://issues.apache.org/jira/browse/OOZIE-3557 OOZIE-3549 Add back support for truststore passwords https://issues.apache.org/jira/browse/OOZIE-3549 OOZIE-3538 oozie-main(pom.xml) plugin maven-surefire-plugin configuration the Tag value is wrong https://issues.apache.org/jira/browse/OOZIE-3538 OOZIE-3482 Fix bug in CoordSubmitXCommand#validateCoordinatorJob https://issues.apache.org/jira/browse/OOZIE-3482 OOZIE-3480 Add windowactionstatus metrics in DBLiteWorkflowStoreService https://issues.apache.org/jira/browse/OOZIE-3480 OOZIE-3461 CoordMaterializeTriggerService code cleanup https://issues.apache.org/jira/browse/OOZIE-3461 OOZIE-3449 Make spark-2 as the default profile https://issues.apache.org/jira/browse/OOZIE-3449 OOZIE-3447 Run test case in local : It shows oozie-hsqldb-orm.xml exception https://issues.apache.org/jira/browse/OOZIE-3447 OOZIE-3418 Upgrade to Guava 27 https://issues.apache.org/jira/browse/OOZIE-3418 OOZIE-3404 The env variable of SPARK_HOME needs to be set when running pySpark https://issues.apache.org/jira/browse/OOZIE-3404 OOZIE-3375 Can't use empty in coordinator https://issues.apache.org/jira/browse/OOZIE-3375 OOZIE-3367 Using && in EL expressions in oozie bundle.xml files generates parse errors https://issues.apache.org/jira/browse/OOZIE-3367 OOZIE-3366 Update workflow status and subworkflow status on suspend command https://issues.apache.org/jira/browse/OOZIE-3366 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3362 When killed, SSH action should kill the spawned processes on target host https://issues.apache.org/jira/browse/OOZIE-3362 OOZIE-3335 Cleanup parseFilter methods https://issues.apache.org/jira/browse/OOZIE-3335 OOZIE-3328 Create Hive compatibility action executor to run hive actions using beeline https://issues.apache.org/jira/browse/OOZIE-3328 OOZIE-3320 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3320 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3254 [coordinator] LAST_ONLY and NONE execution modes: possible OutOfMemoryError when there are too many coordinator actions to materialize https://issues.apache.org/jira/browse/OOZIE-3254 OOZIE-3199 Let system property restriction configurable https://issues.apache.org/jira/browse/OOZIE-3199 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3137 Add support for log4j2 in HiveMain https://issues.apache.org/jira/browse/OOZIE-3137 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 OOZIE-3091 Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: org/apache/avro/mapred/AvroWrapper" https://issues.apache.org/jira/browse/OOZIE-3091 OOZIE-3071 Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than Spark 2.2.0 https://issues.apache.org/jira/browse/OOZIE-3071 OOZIE-3063 Sanitizing variables that are part of openjpa.ConnectionProperties https://issues.apache.org/jira/browse/OOZIE-3063 OOZIE-3062 Set HADOOP_CONF_DIR for spark action https://issues.apache.org/jira/browse/OOZIE-3062 OOZIE-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2834 ParameterVerifier logging non-useful warning for workflow definition https://issues.apache.org/jira/browse/OOZIE-2834 OOZIE-2812 SparkConfigurationService should support loading configurations from multiple Spark versions
[jira] [Created] (OOZIE-3564) Upgrade to JSP EL 3.0
Rohini Palaniswamy created OOZIE-3564: - Summary: Upgrade to JSP EL 3.0 Key: OOZIE-3564 URL: https://issues.apache.org/jira/browse/OOZIE-3564 Project: Oozie Issue Type: Improvement Reporter: Rohini Palaniswamy Currently Oozie EL functions are implemented with JSP EL 2.0. Should consider upgrading to EL 3.0 which has more features https://www.baeldung.com/jsf-expression-language-el-3 https://www.ibm.com/support/knowledgecenter/en/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/cwlp_el30.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords
[ https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982694#comment-16982694 ] Hadoop QA commented on OOZIE-3549: -- Testing JIRA OOZIE-3549 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:red}-1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:red}-1{color} the patch contains 1 line(s) with trailing spaces .{color:green}+1{color} the patch does not introduce any star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:green}+1{color} There are no new bugs found in total. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:green}+1{color} There are no new bugs found in [core]. .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:green}+1{color} There are no new bugs found in [sharelib/oozie]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [tools]. .{color:green}+1{color} There are no new bugs found in [server]. .{color:green}+1{color} There are no new bugs found in [client]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [webapp]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:red}-1 TESTS{color} .Tests run: 3194 .Tests failed : 9 .Tests in error : 0 .Tests timed out : 0 {color:red}-1{color} [ERROR] There are [9] test failures in [server]. Listing only the first [5] ones emptyIncludeCipherSuitesAreNotSet:org.apache.oozie.server.TestSSLServerConnectorFactory includeCipherSuitesCanBeSetViaConfig:org.apache.oozie.server.TestSSLServerConnectorFactory testHSTSDefault:org.apache.oozie.server.TestSSLServerConnectorFactory excludeCipherSuitesCanBeSetViaConfig:org.apache.oozie.server.TestSSLServerConnectorFactory excludeProtocolsCanBeSetViaConfig:org.apache.oozie.server.TestSSLServerConnectorFactory Check console output for the full list of errors/failures {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/1256/ > Add back support for truststore passwords > - > > Key: OOZIE-3549 > URL: https://issues.apache.org/jira/browse/OOZIE-3549 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Major > Attachments: OOZIE-3549-v2.patch, OOZIE-3549.patch > > > OOZIE-3157 removed {{oozie.https.truststore.pass}} property, because we > (Oozie + Jetty) don't write the truststore and the password is not required > for reading. > This is no longer true, Java 11's keytool now defaults to creating PKCS12 > keystores instead of JKS, and according to > [this|https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771363] > bug description "A JKS keystore can be read without supplying a password (or > by supplying an
Failed: OOZIE-3549 PreCommit Build #1256
Jira: https://issues.apache.org/jira/browse/OOZIE-3549 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1256/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 2.27 MB...] [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS xargs: WARNING: a NUL character occurred in the input. It cannot be passed through in the argument list. Did you mean to use the --null option? Running test-patch task DISTRO Running test-patch task MODERNIZER Running modernizer op=report [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt [TRACE] Modernizer errors before patch: 51 [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt [TRACE] Modernizer errors after patch: 51 Testing JIRA OOZIE-3549 Cleaning local git workspace +1 PATCH_APPLIES +1 CLEAN -1 RAW_PATCH_ANALYSIS +1 the patch does not introduce any @author tags +1 the patch does not introduce any tabs -1 the patch contains 1 line(s) with trailing spaces +1 the patch does not introduce any star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings +1 There are no new bugs found in total. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [core]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [tools]. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [webapp]. +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files -1 TESTS Tests run: 3194 Tests failed : 9 Tests in error : 0 Tests timed out : 0 -1 [ERROR] There are [9] test failures in [server]. Listing only the first [5] ones emptyIncludeCipherSuitesAreNotSet:org.apache.oozie.server.TestSSLServerConnectorFactory includeCipherSuitesCanBeSetViaConfig:org.apache.oozie.server.TestSSLServerConnectorFactory testHSTSDefault:org.apache.oozie.server.TestSSLServerConnectorFactory excludeCipherSuitesCanBeSetViaConfig:org.apache.oozie.server.TestSSLServerConnectorFactory excludeProtocolsCanBeSetViaConfig:org.apache.oozie.server.TestSSLServerConnectorFactory Check console output for the full list of errors/failures +1 DISTRO +1 distro tarball builds with the patch +1 MODERNIZER -1 Overall result, please check the reported -1(s) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1256/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 39080 0 100 3908 0 2594 0:00:01 0:00:01 --:--:--
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982646#comment-16982646 ] ASF subversion and git services commented on OOZIE-3491: Commit d69712aee0ea118121cc0101484204f3b88089ee in oozie's branch refs/heads/master from Andras Salamon [ https://gitbox.apache.org/repos/asf?p=oozie.git;h=d69712a ] OOZIE-3491 Confusing System ID error message (matijhs via asalamon74) > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491-V3.patch, > OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982626#comment-16982626 ] Hadoop QA commented on OOZIE-3491: -- Testing JIRA OOZIE-3491 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:red}-1{color} There are [21] new bugs found below threshold in total that must be fixed. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/oozie]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [server]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:green}+1{color} There are no new bugs found in [webapp]. .{color:red}-1{color} There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The top [5] most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] .At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] .{color:red}-1{color} There are [15] new bugs found below threshold in [tools] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): tools/findbugs-new.html .The top [5] most important SpotBugs errors are: .At OozieDBCLI.java:[line 584]: This use of java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL injection .At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573] .At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575] .At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578] .At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581] .{color:green}+1{color} There are no new bugs found in [client]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 3194 .{color:orange}Tests failed at first run:{color} TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator .For the complete list of flaky tests, see TEST-SUMMARY-FULL files. {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available
Failed: OOZIE-3491 PreCommit Build #1255
Jira: https://issues.apache.org/jira/browse/OOZIE-3491 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1255/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 2.15 MB...] Running test-patch task MODERNIZER Running modernizer op=report [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt [TRACE] Modernizer errors before patch: 51 [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt [TRACE] Modernizer errors after patch: 51 Testing JIRA OOZIE-3491 Cleaning local git workspace +1 PATCH_APPLIES +1 CLEAN +1 RAW_PATCH_ANALYSIS +1 the patch does not introduce any @author tags +1 the patch does not introduce any tabs +1 the patch does not introduce any trailing spaces +1 the patch does not introduce any star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings -1 There are [21] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [webapp]. -1 There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The top [5] most important SpotBugs errors are: At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] -1 There are [15] new bugs found below threshold in [tools] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): tools/findbugs-new.html The top [5] most important SpotBugs errors are: At OozieDBCLI.java:[line 584]: This use of java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL injection At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573] At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575] At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578] At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581] +1 There are no new bugs found in [client]. +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files +1 TESTS Tests run: 3194 Tests failed at first run: TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator For the complete list of flaky tests, see TEST-SUMMARY-FULL files. +1 DISTRO +1 distro tarball builds with the patch +1 MODERNIZER -1 Overall result, please check the reported -1(s) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1255/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 49070 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 49070 0 100 4907 0 3264 0:00:01
Failed: OOZIE-3561 PreCommit Build #1254
Jira: https://issues.apache.org/jira/browse/OOZIE-3561 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1254/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 2.15 MB...] [DEBUG] You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html [ERROR] There are [4] new bugs found below threshold in total that must be fixed. [TRACE] SpotBugs diffs checked and reports created [TRACE] Summary file size is 3335 bytes [TRACE] Full summary file size is 2951 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Running test-patch task MODERNIZER Running modernizer op=report [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt [TRACE] Modernizer errors before patch: 51 [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt [TRACE] Modernizer errors after patch: 51 Testing JIRA OOZIE-3561 Cleaning local git workspace +1 PATCH_APPLIES +1 CLEAN +1 RAW_PATCH_ANALYSIS +1 the patch does not introduce any @author tags +1 the patch does not introduce any tabs +1 the patch does not introduce any trailing spaces +1 the patch does not introduce any star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings -1 There are [4] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [webapp]. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [tools]. +1 There are no new bugs found in [server]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [client]. -1 There are [4] new bugs found below threshold in [core] that must be fixed. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The most important SpotBugs errors are: At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a file whose location might be specified by user input: At BulkJPAExecutor.java:[line 206] At AuthorizationService.java:[line 189]: At AuthorizationService.java:[line 192] +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files +1 TESTS Tests run: 3197 +1 DISTRO +1 distro tarball builds with the patch +1 MODERNIZER -1 Overall result, please check the reported -1(s) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1254/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 40320 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 40320 0 100 4032 0 2394 0:00:01 0:00:01 --:--:--
[jira] [Commented] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982620#comment-16982620 ] Hadoop QA commented on OOZIE-3561: -- Testing JIRA OOZIE-3561 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:red}-1{color} There are [4] new bugs found below threshold in total that must be fixed. .{color:green}+1{color} There are no new bugs found in [webapp]. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/oozie]. .{color:green}+1{color} There are no new bugs found in [tools]. .{color:green}+1{color} There are no new bugs found in [server]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:green}+1{color} There are no new bugs found in [client]. .{color:red}-1{color} There are [4] new bugs found below threshold in [core] that must be fixed. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .java/io/File.init(Ljava/lang/String;Ljava/lang/String;)V reads a file whose location might be specified by user input: At BulkJPAExecutor.java:[line 206] .At AuthorizationService.java:[line 189]: At AuthorizationService.java:[line 192] {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 3197 {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/1254/ > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982589#comment-16982589 ] Hadoop QA commented on OOZIE-3491: -- Testing JIRA OOZIE-3491 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:red}-1{color} There are [21] new bugs found below threshold in total that must be fixed. .{color:red}-1{color} There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The top [5] most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] .At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] .{color:red}-1{color} There are [15] new bugs found below threshold in [tools] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): tools/findbugs-new.html .The top [5] most important SpotBugs errors are: .At OozieDBCLI.java:[line 584]: This use of java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL injection .At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573] .At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575] .At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578] .At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581] .{color:green}+1{color} There are no new bugs found in [docs]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/oozie]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [webapp]. .{color:green}+1{color} There are no new bugs found in [client]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [server]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 3194 {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/1253/ > Confusing System ID error message > - > > Key: OOZIE-3491 >
Failed: OOZIE-3491 PreCommit Build #1253
Jira: https://issues.apache.org/jira/browse/OOZIE-3491 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1253/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 2.15 MB...] Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Running test-patch task MODERNIZER Running modernizer op=report [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt [TRACE] Modernizer errors before patch: 51 [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt [TRACE] Modernizer errors after patch: 51 Testing JIRA OOZIE-3491 Cleaning local git workspace +1 PATCH_APPLIES +1 CLEAN +1 RAW_PATCH_ANALYSIS +1 the patch does not introduce any @author tags +1 the patch does not introduce any tabs +1 the patch does not introduce any trailing spaces +1 the patch does not introduce any star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings -1 There are [21] new bugs found below threshold in total that must be fixed. -1 There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The top [5] most important SpotBugs errors are: At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] -1 There are [15] new bugs found below threshold in [tools] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): tools/findbugs-new.html The top [5] most important SpotBugs errors are: At OozieDBCLI.java:[line 584]: This use of java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL injection At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573] At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575] At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578] At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581] +1 There are no new bugs found in [docs]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [webapp]. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [server]. +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files +1 TESTS Tests run: 3194 +1 DISTRO +1 distro tarball builds with the patch +1 MODERNIZER -1 Overall result, please check the reported -1(s) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1253/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 47090 0 100 4709 0 3116 0:00:01 0:00:01 --:--:--
[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords
[ https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982588#comment-16982588 ] Hadoop QA commented on OOZIE-3549: -- PreCommit-OOZIE-Build started > Add back support for truststore passwords > - > > Key: OOZIE-3549 > URL: https://issues.apache.org/jira/browse/OOZIE-3549 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Major > Attachments: OOZIE-3549-v2.patch, OOZIE-3549.patch > > > OOZIE-3157 removed {{oozie.https.truststore.pass}} property, because we > (Oozie + Jetty) don't write the truststore and the password is not required > for reading. > This is no longer true, Java 11's keytool now defaults to creating PKCS12 > keystores instead of JKS, and according to > [this|https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771363] > bug description "A JKS keystore can be read without supplying a password (or > by supplying an empty one) while a PKCS12 keystore requires a password to be > set." > We should reintroduce this property and allow the it again to specify this > password and pass it to jetty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3549) Add back support for truststore passwords
[ https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Juhasz updated OOZIE-3549: --- Attachment: OOZIE-3549-v2.patch > Add back support for truststore passwords > - > > Key: OOZIE-3549 > URL: https://issues.apache.org/jira/browse/OOZIE-3549 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Major > Attachments: OOZIE-3549-v2.patch, OOZIE-3549.patch > > > OOZIE-3157 removed {{oozie.https.truststore.pass}} property, because we > (Oozie + Jetty) don't write the truststore and the password is not required > for reading. > This is no longer true, Java 11's keytool now defaults to creating PKCS12 > keystores instead of JKS, and according to > [this|https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771363] > bug description "A JKS keystore can be read without supplying a password (or > by supplying an empty one) while a PKCS12 keystore requires a password to be > set." > We should reintroduce this property and allow the it again to specify this > password and pass it to jetty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3549) Add back support for truststore passwords
[ https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Juhasz updated OOZIE-3549: --- Attachment: (was: OOZIE-3549-v2.patch) > Add back support for truststore passwords > - > > Key: OOZIE-3549 > URL: https://issues.apache.org/jira/browse/OOZIE-3549 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Major > Attachments: OOZIE-3549-v2.patch, OOZIE-3549.patch > > > OOZIE-3157 removed {{oozie.https.truststore.pass}} property, because we > (Oozie + Jetty) don't write the truststore and the password is not required > for reading. > This is no longer true, Java 11's keytool now defaults to creating PKCS12 > keystores instead of JKS, and according to > [this|https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771363] > bug description "A JKS keystore can be read without supplying a password (or > by supplying an empty one) while a PKCS12 keystore requires a password to be > set." > We should reintroduce this property and allow the it again to specify this > password and pass it to jetty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3549) Add back support for truststore passwords
[ https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Juhasz updated OOZIE-3549: --- Attachment: OOZIE-3549-v2.patch > Add back support for truststore passwords > - > > Key: OOZIE-3549 > URL: https://issues.apache.org/jira/browse/OOZIE-3549 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Major > Attachments: OOZIE-3549-v2.patch, OOZIE-3549.patch > > > OOZIE-3157 removed {{oozie.https.truststore.pass}} property, because we > (Oozie + Jetty) don't write the truststore and the password is not required > for reading. > This is no longer true, Java 11's keytool now defaults to creating PKCS12 > keystores instead of JKS, and according to > [this|https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771363] > bug description "A JKS keystore can be read without supplying a password (or > by supplying an empty one) while a PKCS12 keystore requires a password to be > set." > We should reintroduce this property and allow the it again to specify this > password and pass it to jetty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords
[ https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982579#comment-16982579 ] Mate Juhasz commented on OOZIE-3549: Uploading a new patch, tested in a deployment. Please see the diff in SSLServerConnectorFactory#setKeystorePass. Some explanation on the relation of KeyManagerPassword and KeyStorePassword from the eclipse docs: https://www.eclipse.org/jetty/documentation/9.3.27.v20190418/configuring-ssl.html#configuring-sslcontextfactory I would say that using a PKCS12 keystore requires the sslContextFactory.KeyStorePassword to be set instead (or besides) of KeyManagerPassword. If jetty's KeyManagerPassword is not set the KeyStorePassword will be used for that as well. > Add back support for truststore passwords > - > > Key: OOZIE-3549 > URL: https://issues.apache.org/jira/browse/OOZIE-3549 > Project: Oozie > Issue Type: Improvement >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Major > Attachments: OOZIE-3549.patch > > > OOZIE-3157 removed {{oozie.https.truststore.pass}} property, because we > (Oozie + Jetty) don't write the truststore and the password is not required > for reading. > This is no longer true, Java 11's keytool now defaults to creating PKCS12 > keystores instead of JKS, and according to > [this|https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1771363] > bug description "A JKS keystore can be read without supplying a password (or > by supplying an empty one) while a PKCS12 keystore requires a password to be > set." > We should reintroduce this property and allow the it again to specify this > password and pass it to jetty. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982576#comment-16982576 ] Hadoop QA commented on OOZIE-3561: -- Testing JIRA OOZIE-3561 Cleaning local git workspace {color:green}+1 PATCH_APPLIES{color} {color:green}+1 CLEAN{color} {color:green}+1 RAW_PATCH_ANALYSIS{color} .{color:green}+1{color} the patch does not introduce any @author tags .{color:green}+1{color} the patch does not introduce any tabs .{color:green}+1{color} the patch does not introduce any trailing spaces .{color:green}+1{color} the patch does not introduce any star imports .{color:green}+1{color} the patch does not introduce any line longer than 132 .{color:green}+1{color} the patch adds/modifies 1 testcase(s) {color:green}+1 RAT{color} .{color:green}+1{color} the patch does not seem to introduce new RAT warnings {color:green}+1 JAVADOC{color} .{color:green}+1{color} Javadoc generation succeeded with the patch .{color:green}+1{color} the patch does not seem to introduce new Javadoc warning(s) {color:green}+1 COMPILE{color} .{color:green}+1{color} HEAD compiles .{color:green}+1{color} patch compiles .{color:green}+1{color} the patch does not seem to introduce new javac warnings {color:red}-1{color} There are [6] new bugs found below threshold in total that must be fixed. .{color:green}+1{color} There are no new bugs found in [fluent-job/fluent-job-api]. .{color:green}+1{color} There are no new bugs found in [docs]. .{color:red}-1{color} There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. .You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html .The top [5] most important SpotBugs errors are: .At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection .At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] .At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] .This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] .At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] .{color:green}+1{color} There are no new bugs found in [sharelib/spark]. .{color:green}+1{color} There are no new bugs found in [sharelib/git]. .{color:green}+1{color} There are no new bugs found in [sharelib/sqoop]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive2]. .{color:green}+1{color} There are no new bugs found in [sharelib/streaming]. .{color:green}+1{color} There are no new bugs found in [sharelib/pig]. .{color:green}+1{color} There are no new bugs found in [sharelib/oozie]. .{color:green}+1{color} There are no new bugs found in [sharelib/hive]. .{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog]. .{color:green}+1{color} There are no new bugs found in [sharelib/distcp]. .{color:green}+1{color} There are no new bugs found in [tools]. .{color:orange}0{color} There are [4] new bugs found in [server] that would be nice to have fixed. .You can find the SpotBugs diff here: server/findbugs-new.html .{color:green}+1{color} There are no new bugs found in [client]. .{color:green}+1{color} There are no new bugs found in [examples]. .{color:green}+1{color} There are no new bugs found in [webapp]. {color:green}+1 BACKWARDS_COMPATIBILITY{color} .{color:green}+1{color} the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations .{color:green}+1{color} the patch does not modify JPA files {color:green}+1 TESTS{color} .Tests run: 3197 {color:green}+1 DISTRO{color} .{color:green}+1{color} distro tarball builds with the patch {color:green}+1 MODERNIZER{color} {color:red}*-1 Overall result, please check the reported -1(s)*{color} The full output of the test-patch run is available at . https://builds.apache.org/job/PreCommit-OOZIE-Build/1252/ > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after
Failed: OOZIE-3561 PreCommit Build #1252
Jira: https://issues.apache.org/jira/browse/OOZIE-3561 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1252/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 2.15 MB...] [ERROR] There are [6] new bugs found below threshold in total that must be fixed. [TRACE] SpotBugs diffs checked and reports created [TRACE] Summary file size is 3482 bytes [TRACE] Full summary file size is 3830 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Running test-patch task MODERNIZER Running modernizer op=report [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-clean.txt [TRACE] Modernizer errors before patch: 51 [TRACE] grep -c '.*ERROR.*Prefer' /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/reports/MODERNIZER-patch.txt [TRACE] Modernizer errors after patch: 51 Testing JIRA OOZIE-3561 Cleaning local git workspace +1 PATCH_APPLIES +1 CLEAN +1 RAW_PATCH_ANALYSIS +1 the patch does not introduce any @author tags +1 the patch does not introduce any tabs +1 the patch does not introduce any trailing spaces +1 the patch does not introduce any star imports +1 the patch does not introduce any line longer than 132 +1 the patch adds/modifies 1 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new Javadoc warning(s) +1 COMPILE +1 HEAD compiles +1 patch compiles +1 the patch does not seem to introduce new javac warnings -1 There are [6] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [docs]. -1 There are [6] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The top [5] most important SpotBugs errors are: At BulkJPAExecutor.java:[line 206]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175] At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199] This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206] At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127] +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [tools]. 0 There are [4] new bugs found in [server] that would be nice to have fixed. You can find the SpotBugs diff here: server/findbugs-new.html +1 There are no new bugs found in [client]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [webapp]. +1 BACKWARDS_COMPATIBILITY +1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient annotations +1 the patch does not modify JPA files +1 TESTS Tests run: 3197 +1 DISTRO +1 distro tarball builds with the patch +1 MODERNIZER -1 Overall result, please check the reported -1(s) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1252/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0 0 00 00 0 0 0 --:--:-- --:--:-- --:--:-- 0100 41800 0 100 4180 0 2764 0:00:01 0:00:01 --:--:--
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982503#comment-16982503 ] Hadoop QA commented on OOZIE-3491: -- PreCommit-OOZIE-Build started > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491-V3.patch, > OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982500#comment-16982500 ] Denes Bodo commented on OOZIE-3561: --- Thank you for the fix [~pbacsko] . I managed to check your change with the original WF which caused the slowness and that worked well and quick. Unfortunately that wf contains sensitive data so I could not share here but the provided 80-action wf is almost the same as the original one. > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated OOZIE-3561: Attachment: (was: OOZIE-3561-004.patch) > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982497#comment-16982497 ] Mate Juhasz commented on OOZIE-3491: Oops, fixed :) thanks > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491-V3.patch, > OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Juhasz updated OOZIE-3491: --- Attachment: OOZIE-3491-V3.patch > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491-V3.patch, > OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982493#comment-16982493 ] Hadoop QA commented on OOZIE-3561: -- PreCommit-OOZIE-Build started > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561-004.patch, OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denes Bodo updated OOZIE-3561: -- Attachment: OOZIE-3561-004.patch > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561-004.patch, OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denes Bodo updated OOZIE-3561: -- Attachment: (was: OOZIE-3561-003.patch) > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denes Bodo updated OOZIE-3561: -- Attachment: OOZIE-3561-003.patch > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561-003.patch, OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982487#comment-16982487 ] Andras Salamon commented on OOZIE-3491: --- Thanks for the new patch [~matijhs], could you please check the other test methods in the {{TestServices}} class? I think it would be better to put the destroy method into a finally block. > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982465#comment-16982465 ] Hadoop QA commented on OOZIE-3491: -- PreCommit-OOZIE-Build started > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3491) Confusing System ID error message
[ https://issues.apache.org/jira/browse/OOZIE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mate Juhasz updated OOZIE-3491: --- Attachment: OOZIE-3491-V2.patch > Confusing System ID error message > - > > Key: OOZIE-3491 > URL: https://issues.apache.org/jira/browse/OOZIE-3491 > Project: Oozie > Issue Type: Bug >Affects Versions: trunk >Reporter: Andras Salamon >Assignee: Mate Juhasz >Priority: Minor > Labels: newbie > Attachments: OOZIE-3491-V2.patch, OOZIE-3491.patch > > > If the System ID is longer than 10 characters Oozie trims it and prints out > an error message: > {noformat} > System ID [oozie-oozi] exceeds maximum length [10], trimming > {noformat} > Which is confusing, because "oozie-oozi" does not exceeds 10 characters. This > is not the original long system ID but the trimmed short one. > I think we should fix the error message and print out both the original and > the new value. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16982457#comment-16982457 ] Hadoop QA commented on OOZIE-3561: -- PreCommit-OOZIE-Build started > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3561) Forkjoin validation is slow when there are many actions in chain
[ https://issues.apache.org/jira/browse/OOZIE-3561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Bacsko updated OOZIE-3561: Attachment: OOZIE-3561-003.patch > Forkjoin validation is slow when there are many actions in chain > > > Key: OOZIE-3561 > URL: https://issues.apache.org/jira/browse/OOZIE-3561 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.1.0 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Critical > Labels: performance > Attachments: OOZIE-3561-002.patch, OOZIE-3561-003.patch, > OOZIE-3561_001.patch > > > In case we have a workflow which has, let's say, 80 actions after each other: > {{a1 -> a2 -> ... a80}} > then the validator code "never" finishes. > Currently the validation (in my understanding) does depth first checks from > the start node and runs in time of n! . This is confirmed as when we split > this huge workflow into two 40-element workflow then we get 2x ~40!-step in > validation instead of ~80! steps. > Guys, could you please confirm or disprove my theory? > Thanks -- This message was sent by Atlassian Jira (v8.3.4#803005)