[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (91 issues) Subscriber: ooziedaily Key Summary OOZIE-3568 Have large amount of log information “WARN messages [main] openjpa.MetaData” in jetty.log need to clean https://issues.apache.org/jira/browse/OOZIE-3568 OOZIE-3567 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3567 OOZIE-3560 IDEA shows have some error in index.jsp https://issues.apache.org/jira/browse/OOZIE-3560 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-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 https://issues.apache.org/jira/browse/OOZIE-2812 OOZIE-2795 Create lib directory or symlink for Oozie CLI during packaging https://issues.apache.org/jira/browse/OOZIE-2795 OOZIE-2784 Include WEEK as a parameter in the Coordinator Expression Language Evaulator https://issues.apache.org/jira/browse/OOZIE-2784 OOZIE-2779 Mask Hive2 action Beeline JDBC password
[jira] [Commented] (OOZIE-3582) Rerun end point returning 401 error
[ https://issues.apache.org/jira/browse/OOZIE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031563#comment-17031563 ] Junfan Zhang commented on OOZIE-3582: - Do you set kerberos true? [~mdbilaly2k] > Rerun end point returning 401 error > --- > > Key: OOZIE-3582 > URL: https://issues.apache.org/jira/browse/OOZIE-3582 > Project: Oozie > Issue Type: Bug > Components: security >Affects Versions: 4.2.0 >Reporter: Mohammed Bilal >Priority: Critical > Fix For: 4.2.0 > > > Hi, > I am making HTTP put request to rerun oozie job, but I am seeing > authorization issue. > I added basic authorization, but no luck. > I referred web API and followed all the steps mentioned there. > [https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Re-Running_a_Workflow_Job] > Here there is no information about any kind of security mechanism which we > need to follow before calling rerun end point. I was able to invoke post > method without any issue to start a oozie job without any authentication. > Could you please provide me more details on how I can fix this issue? > Error Log: > org.springframework.web.client.HttpClientErrorException: 401 > Unauthorizedorg.springframework.web.client.HttpClientErrorException: 401 > Unauthorized at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:94) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:79) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:775) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:728) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.execute(RestTemplate.java:694) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.put(RestTemplate.java:503) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] > Thank you! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (OOZIE-1516) Usability issues submitting jobs
[ https://issues.apache.org/jira/browse/OOZIE-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Salamon resolved OOZIE-1516. --- Resolution: Not A Bug This is a very issue which was never confirmed. Closing. > Usability issues submitting jobs > > > Key: OOZIE-1516 > URL: https://issues.apache.org/jira/browse/OOZIE-1516 > Project: Oozie > Issue Type: Improvement > Components: examples > Environment: Cloudera CDH4 latest on Centos >Reporter: Brad Cox >Priority: Critical > > J Harsh suggested filing a usability issue concerning a problem he helped me > resolve via email. Problem seems to boil down to differences between > localhost and localhost.localdomain that I don't understand well enough to > explain here. I've enclosed the email thread as documentation. > J Harsh... > I believe we seem to be doing a strict hostname check in Apache Oozie > and not a resolving check. Could you report an improvement on the > Apache Oozie JIRA (https://issues.apache.org/jira/browse/OOZIE) > upstream to perhaps improve this for usability? > On Sun, Sep 1, 2013 at 2:41 AM, Brad Cox wrote: > Copied examples to /user/cloudera/examples and changed nameNode to > hdfs://localhost.localdomain in job.properties. Results look like a good > sign. > [cloudera@localhost Desktop]$ oozie job -oozie http://localhost:11000/oozie > -config examples/apps/map-reduce/job.properties -run > job: 000-130831130415538-oozie-oozi-W > But in oozie console, got a job fail because jobTracker's not in whitelist > so changed that to just localhost.localdomain by analogy. > [cloudera@localhost Desktop]$ oozie job -oozie http://localhost:11000/oozie > -config examples/apps/map-reduce/job.properties -run > job: 001-130831130415538-oozie-oozi-W > Console says that try succeeded. So thanks for the help!! > All I'm missing is an understanding of why cloudera comes outOfBox with some > services configured as localhost and others localhost.localdomain. I always > thought they were equivalent. But these are huge differences; success vs > fail. > On Aug 31, 2013, at 4:58 PM, Brad Cox wrote: > You mean use localhost.localdomain instead of localhost? Or should I define > a unique name with hostname cmd, restart all, and use that instead? > [cloudera@localhost Desktop]$ hostname > localhost.localdomain > On Aug 31, 2013, at 4:54 PM, Harsh J wrote: > The whitelist message is close to the solution. Do not use 'localhost' > in your job.properties, but replace it with whatever the command > 'hostname' produces on your terminal, and I believe it should do the > trick. > On Sat, Aug 31, 2013 at 11:11 PM, Brad Cox wrote: > That's what I tried in previous attempts. That causes this > oozie job -oozie http://localhost:11000/oozie -config > examples/apps/map-reduce/job.properties -run > Error: HTTP error code: 500 : Internal Server Error > /var/log/lochost.date.log contains > Caused by: java.net.URISyntaxException: Relative path in absolute URI: > localhost:8020/user/cloudera/examples/apps/map-reduce > at java.net.URI.checkPath(URI.java:1788) > examples is where I put it as you said > [cloudera@localhost Desktop]$ hdfs dfs -ls / > Found 8 items > drwxr-xr-x - hdfs supergroup 0 2013-08-30 15:28 /accumulo > drwxr-xr-x - oozie supergroup 0 2013-08-31 04:52 /examples > drwxr-xr-x - hbase hbase 0 2013-08-31 07:22 /hbase > drwxr-xr-x - hdfs supergroup 0 2013-08-30 16:38 /share > drwxr-xr-x - solr solr0 2013-07-17 00:03 /solr > drwxrwxrwx - hdfs supergroup 0 2013-08-30 16:32 /tmp > drwxr-xr-x - hdfs supergroup 0 2013-08-30 16:32 /user > drwxr-xr-x - hdfs supergroup 0 2013-07-17 00:03 /var > All this is after hacking nameNode=localhost:8020 (was hdfs://...) in > job.properties based on the Running the Examples section of the Oozie docs. > On reverting that change, the message changed to the problem I had before: > oozie job -oozie http://localhost:11000/oozie -config > examples/apps/map-reduce/job.properties -run > Error: E0901 : E0901: Namenode [localhost:8020] not allowed, not in Oozies > whitelist > Based on that msg, I'd already changed > oozie.service.HadoopAccessorService.nameNode.whitelist to localhost:8020 in > /etc/oozie/conf/oozie-site.xml and just made a similar change to > jobTracker.whitelist to localhost:8021. Best I've been able to do is switch > mystifying messages. > On Aug 31, 2013, at 12:22 PM, Harsh J wrote: > Hi Brad, > In Oozie, an simple "application" consists of a directory on HDFS that > carries workflow.xml, and associated libraries/files. > To invoke an instance of such an application, we use a local > job.properties file that carries any variable parameter values, to > begin the application with. > Typically, to run the examples
[jira] [Commented] (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?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031509#comment-17031509 ] Andras Salamon commented on OOZIE-3071: --- [~matijhs] Thanks for the bump. (To repeat [~gezapeti]'s question): What will happen with Spark1 if we bump commons-lang3 version? It would be great if you could test it. We already have problems with the different requirements of spark-1 and spark-2. It's not too nice, but we already have spark-1 and spark-2 profiles, maybe we could try to update commons-lang3 and we could specify the old one in spark-1 if it's required. > Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than > Spark 2.2.0 > > > Key: OOZIE-3071 > URL: https://issues.apache.org/jira/browse/OOZIE-3071 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 4.3.0 >Reporter: Ran Gu >Assignee: Artem Ervits >Priority: Major > Labels: patch > Attachments: OOZIE-3071-1.patch, OOZIE-3071.patch > > > Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib. > Spark 2.2.0 uses commons-lang3 version 3.5. > This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters. > Error message: > 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: > java.lang.IllegalArgumentException: Illegal pattern component: XXX > java.lang.IllegalArgumentException: Illegal pattern component: XXX > at > org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282) > at > org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149) > at > org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142) > at > org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384) > at > org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369) > at > org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91) > at > org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88) > at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OOZIE-3583) NoSuchMethodError: org.apache.hadoop.io.IOUtils.readFullyToByteArray
jiama created OOZIE-3583: Summary: NoSuchMethodError: org.apache.hadoop.io.IOUtils.readFullyToByteArray Key: OOZIE-3583 URL: https://issues.apache.org/jira/browse/OOZIE-3583 Project: Oozie Issue Type: Bug Affects Versions: 5.1.0 Environment: cloudera6.2 oozie5.1 spark2.4 on yarn3 Reporter: jiama Exception in thread "main" java.lang.NoSuchMethodError: org.apache.hadoop.io.IOUtils.readFullyToByteArray(Ljava/io/DataInput;)[B at org.apache.hadoop.yarn.security.AMRMTokenIdentifier.readFields(AMRMTokenIdentifier.java:89) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031482#comment-17031482
]
Hadoop QA commented on OOZIE-3071:
--
Testing JIRA OOZIE-3071
Cleaning local git workspace
{color:red}-1{color} Patch failed to apply to head of branch
> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than
> Spark 2.2.0
>
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>Assignee: Artem Ervits
>Priority: Major
> Labels: patch
> Attachments: OOZIE-3071-1.patch, OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5.
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception:
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
Failed: OOZIE-3071 PreCommit Build #1300
Jira: https://issues.apache.org/jira/browse/OOZIE-3071 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1300/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 902.28 KB...] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) @ oozie-distro --- [INFO] [INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ oozie-distro --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/distro/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- modernizer-maven-plugin:1.8.0:modernizer (default-cli) @ oozie-distro --- [INFO] [INFO] --< org.apache.oozie:oozie-zookeeper-security-tests >--- [INFO] Building Apache Oozie ZooKeeper Security Tests 5.3.0-SNAPSHOT[25/25] [INFO] [ jar ]- [INFO] [INFO] --- maven-clean-plugin:3.0.0:clean (default-clean) @ oozie-zookeeper-security-tests --- [INFO] Deleting /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/target [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) @ oozie-zookeeper-security-tests --- [INFO] [INFO] --- maven-resources-plugin:3.0.2:resources (default-resources) @ oozie-zookeeper-security-tests --- [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/zookeeper-security-tests/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:3.7.0:compile (default-compile) @ oozie-zookeeper-security-tests --- [INFO] No sources to compile [INFO] [INFO] --- modernizer-maven-plugin:1.8.0:modernizer (default-cli) @ oozie-zookeeper-security-tests --- [INFO] [INFO] Reactor Summary for Apache Oozie Main 5.3.0-SNAPSHOT: [INFO] [INFO] Apache Oozie Main .. SUCCESS [ 1.246 s] [INFO] Apache Oozie Fluent Job SUCCESS [ 0.080 s] [INFO] Apache Oozie Fluent Job API SUCCESS [ 7.865 s] [INFO] Apache Oozie Client SUCCESS [ 1.588 s] [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [ 1.262 s] [INFO] Apache Oozie Share Lib HCatalog SUCCESS [ 0.971 s] [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [ 0.331 s] [INFO] Apache Oozie Core .. SUCCESS [ 10.089 s] [INFO] Apache Oozie Share Lib Streaming ... SUCCESS [ 2.085 s] [INFO] Apache Oozie Share Lib Pig . SUCCESS [ 1.536 s] [INFO] Apache Oozie Share Lib Git . SUCCESS [ 1.930 s] [INFO] Apache Oozie Share Lib Hive SUCCESS [ 0.983 s] [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS [ 1.897 s] [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS [ 1.800 s] [INFO] Apache Oozie Examples .. SUCCESS [ 1.908 s] [INFO] Apache Oozie Share Lib Spark ... SUCCESS [ 2.779 s] [INFO] Apache Oozie Share Lib . SUCCESS [ 0.026 s] [INFO] Apache Oozie Docs .. SUCCESS [ 0.043 s] [INFO] Apache Oozie WebApp SUCCESS [ 2.150 s] [INFO] Apache Oozie Tools . SUCCESS [ 1.294 s] [INFO] Apache Oozie MiniOozie . SUCCESS [ 1.355 s] [INFO] Apache Oozie Fluent Job Client . SUCCESS [ 1.128 s] [INFO] Apache Oozie Server SUCCESS [ 2.124 s] [INFO] Apache Oozie Distro SUCCESS [ 1.676 s] [INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [ 1.877 s] [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 51.732 s [INFO] Finished at: 2020-02-06T11:18:46Z [INFO] EXITVALUE 0 [TRACE] Modernizer output in HEAD verified and saved Applying patch Checking patch pom.xml... error: while searching for: org.apache.commons commons-lang3 3.3.2 error: patch failed: pom.xml:1308 error: pom.xml: patch does not apply error: git diff header lacks filename
[jira] [Commented] (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?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031480#comment-17031480 ] Hadoop QA commented on OOZIE-3071: -- PreCommit-OOZIE-Build started > Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than > Spark 2.2.0 > > > Key: OOZIE-3071 > URL: https://issues.apache.org/jira/browse/OOZIE-3071 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 4.3.0 >Reporter: Ran Gu >Assignee: Artem Ervits >Priority: Major > Labels: patch > Attachments: OOZIE-3071-1.patch, OOZIE-3071.patch > > > Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib. > Spark 2.2.0 uses commons-lang3 version 3.5. > This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters. > Error message: > 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception: > java.lang.IllegalArgumentException: Illegal pattern component: XXX > java.lang.IllegalArgumentException: Illegal pattern component: XXX > at > org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282) > at > org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149) > at > org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142) > at > org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384) > at > org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369) > at > org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91) > at > org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88) > at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82) -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (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?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031477#comment-17031477
]
Mate Juhasz commented on OOZIE-3071:
Bumping up the topic again... commons-lang3 3.3.2 does not support JDK 11, the
below error can be observed when running spark actions on Java 11.
{noformat}
Caused by: java.lang.NullPointerException
at
org.apache.commons.lang3.SystemUtils.isJavaVersionAtLeast(SystemUtils.java:1654)
{noformat}
commons-lang3:3.8.1 fixes it, but we should use the same 3.9 as in SPARK-30035,
which is the first release to support JDK9+.
> Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 than
> Spark 2.2.0
>
>
> Key: OOZIE-3071
> URL: https://issues.apache.org/jira/browse/OOZIE-3071
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 4.3.0
>Reporter: Ran Gu
>Assignee: Artem Ervits
>Priority: Major
> Labels: patch
> Attachments: OOZIE-3071-1.patch, OOZIE-3071.patch
>
>
> Currently Oozie 4.3.0 uses commons-lang3 version 3.3.2 in Spark sharelib.
> Spark 2.2.0 uses commons-lang3 version 3.5.
> This causes Oozie(/Spark) job failures on EMR-5.8.0 clusters.
> Error message:
> 17/08/22 00:22:43 ERROR ApplicationMaster: User class threw exception:
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> java.lang.IllegalArgumentException: Illegal pattern component: XXX
> at
> org.apache.commons.lang3.time.FastDatePrinter.parsePattern(FastDatePrinter.java:282)
> at
> org.apache.commons.lang3.time.FastDatePrinter.init(FastDatePrinter.java:149)
> at
> org.apache.commons.lang3.time.FastDatePrinter.(FastDatePrinter.java:142)
> at
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:384)
> at
> org.apache.commons.lang3.time.FastDateFormat.(FastDateFormat.java:369)
> at
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:91)
> at
> org.apache.commons.lang3.time.FastDateFormat$1.createInstance(FastDateFormat.java:88)
> at org.apache.commons.lang3.time.FormatCache.getInstance(FormatCache.java:82)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (OOZIE-3582) Rerun end point returning 401 error
[ https://issues.apache.org/jira/browse/OOZIE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031472#comment-17031472 ] Kinga Marton commented on OOZIE-3582: - [~mdbilaly2k], have you faced this issue with the latest Oozie (5.2.0) as well? > Rerun end point returning 401 error > --- > > Key: OOZIE-3582 > URL: https://issues.apache.org/jira/browse/OOZIE-3582 > Project: Oozie > Issue Type: Bug > Components: security >Affects Versions: 4.2.0 >Reporter: Mohammed Bilal >Priority: Critical > Fix For: 4.2.0 > > > Hi, > I am making HTTP put request to rerun oozie job, but I am seeing > authorization issue. > I added basic authorization, but no luck. > I referred web API and followed all the steps mentioned there. > [https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Re-Running_a_Workflow_Job] > Here there is no information about any kind of security mechanism which we > need to follow before calling rerun end point. I was able to invoke post > method without any issue to start a oozie job without any authentication. > Could you please provide me more details on how I can fix this issue? > Error Log: > org.springframework.web.client.HttpClientErrorException: 401 > Unauthorizedorg.springframework.web.client.HttpClientErrorException: 401 > Unauthorized at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:94) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:79) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:775) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:728) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.execute(RestTemplate.java:694) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.put(RestTemplate.java:503) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] > Thank you! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3582) Rerun end point returning 401 error
[ https://issues.apache.org/jira/browse/OOZIE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammed Bilal updated OOZIE-3582: -- Priority: Critical (was: Major) > Rerun end point returning 401 error > --- > > Key: OOZIE-3582 > URL: https://issues.apache.org/jira/browse/OOZIE-3582 > Project: Oozie > Issue Type: Bug > Components: security >Affects Versions: 4.2.0 >Reporter: Mohammed Bilal >Priority: Critical > Fix For: 4.2.0 > > > Hi, > I am making HTTP put request to rerun oozie job, but I am seeing > authorization issue. > I added basic authorization, but no luck. > I referred web API and followed all the steps mentioned there. > [https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Re-Running_a_Workflow_Job] > Here there is no information about any kind of security mechanism which we > need to follow before calling rerun end point. I was able to invoke post > method without any issue to start a oozie job without any authentication. > Could you please provide me more details on how I can fix this issue? > Error Log: > org.springframework.web.client.HttpClientErrorException: 401 > Unauthorizedorg.springframework.web.client.HttpClientErrorException: 401 > Unauthorized at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:94) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:79) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:775) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:728) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.execute(RestTemplate.java:694) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.put(RestTemplate.java:503) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] > Thank you! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (OOZIE-3582) Rerun end point returning 401 error
[ https://issues.apache.org/jira/browse/OOZIE-3582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mohammed Bilal updated OOZIE-3582: -- Issue Type: Bug (was: Test) > Rerun end point returning 401 error > --- > > Key: OOZIE-3582 > URL: https://issues.apache.org/jira/browse/OOZIE-3582 > Project: Oozie > Issue Type: Bug > Components: security >Affects Versions: 4.2.0 >Reporter: Mohammed Bilal >Priority: Major > Fix For: 4.2.0 > > > Hi, > I am making HTTP put request to rerun oozie job, but I am seeing > authorization issue. > I added basic authorization, but no luck. > I referred web API and followed all the steps mentioned there. > [https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Re-Running_a_Workflow_Job] > Here there is no information about any kind of security mechanism which we > need to follow before calling rerun end point. I was able to invoke post > method without any issue to start a oozie job without any authentication. > Could you please provide me more details on how I can fix this issue? > Error Log: > org.springframework.web.client.HttpClientErrorException: 401 > Unauthorizedorg.springframework.web.client.HttpClientErrorException: 401 > Unauthorized at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:94) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:79) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:775) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:728) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.execute(RestTemplate.java:694) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at > org.springframework.web.client.RestTemplate.put(RestTemplate.java:503) > ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] > Thank you! > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (OOZIE-3582) Rerun end point returning 401 error
Mohammed Bilal created OOZIE-3582: - Summary: Rerun end point returning 401 error Key: OOZIE-3582 URL: https://issues.apache.org/jira/browse/OOZIE-3582 Project: Oozie Issue Type: Test Components: security Affects Versions: 4.2.0 Reporter: Mohammed Bilal Fix For: 4.2.0 Hi, I am making HTTP put request to rerun oozie job, but I am seeing authorization issue. I added basic authorization, but no luck. I referred web API and followed all the steps mentioned there. [https://oozie.apache.org/docs/4.2.0/WebServicesAPI.html#Re-Running_a_Workflow_Job] Here there is no information about any kind of security mechanism which we need to follow before calling rerun end point. I was able to invoke post method without any issue to start a oozie job without any authentication. Could you please provide me more details on how I can fix this issue? Error Log: org.springframework.web.client.HttpClientErrorException: 401 Unauthorizedorg.springframework.web.client.HttpClientErrorException: 401 Unauthorized at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:94) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at org.springframework.web.client.DefaultResponseErrorHandler.handleError(DefaultResponseErrorHandler.java:79) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at org.springframework.web.client.ResponseErrorHandler.handleError(ResponseErrorHandler.java:63) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at org.springframework.web.client.RestTemplate.handleResponse(RestTemplate.java:775) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:728) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:694) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] at org.springframework.web.client.RestTemplate.put(RestTemplate.java:503) ~[spring-web-5.0.5.RELEASE.jar:5.0.5.RELEASE] Thank you! -- This message was sent by Atlassian Jira (v8.3.4#803005)
