[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (46 issues) Subscriber: ooziedaily Key Summary OOZIE-2171 Some error code messages are not parsed correctly due to unescaped single quote https://issues.apache.org/jira/browse/OOZIE-2171 OOZIE-2169 Fix return type for fs:dirSize, fs:fileSize and fs:blockSize in WF spec https://issues.apache.org/jira/browse/OOZIE-2169 OOZIE-2168 Oozie flow and action names have 50 char limit https://issues.apache.org/jira/browse/OOZIE-2168 OOZIE-2134 Remove references to Services.get().getConf() in code https://issues.apache.org/jira/browse/OOZIE-2134 OOZIE-2130 Add EL Function for offsetting a date by a timezone amount including DST https://issues.apache.org/jira/browse/OOZIE-2130 OOZIE-2129 Duplicate child jobs per instance https://issues.apache.org/jira/browse/OOZIE-2129 OOZIE-2106 Make tomcat download url configurable in the pom file https://issues.apache.org/jira/browse/OOZIE-2106 OOZIE-2105 Make version of submodules configurable with parent version https://issues.apache.org/jira/browse/OOZIE-2105 OOZIE-2099 Add test-patch support for patches generated without --no-prefix https://issues.apache.org/jira/browse/OOZIE-2099 OOZIE-2081 WorkflowJob notification to include coordinator action id https://issues.apache.org/jira/browse/OOZIE-2081 OOZIE-2060 Incorrect documentation of Java action config XML filename https://issues.apache.org/jira/browse/OOZIE-2060 OOZIE-2051 Allows multiple default action configuration files per action https://issues.apache.org/jira/browse/OOZIE-2051 OOZIE-2044 ssh action succeed with a not exists command which should be fail. https://issues.apache.org/jira/browse/OOZIE-2044 OOZIE-2030 Configuration properties from global section is not getting set in Hadoop job conf when using sub-workflow action in Oozie workflow.xml https://issues.apache.org/jira/browse/OOZIE-2030 OOZIE-1980 Sql error should not fail coord job https://issues.apache.org/jira/browse/OOZIE-1980 OOZIE-1977 Display patch analysis issues https://issues.apache.org/jira/browse/OOZIE-1977 OOZIE-1936 Queuedump command should display queue information for all server. https://issues.apache.org/jira/browse/OOZIE-1936 OOZIE-1931 Admin command to print all locks held by server(s) https://issues.apache.org/jira/browse/OOZIE-1931 OOZIE-1927 Use StoreStatusFilter for WorkflowsJobGetJPAExecutor https://issues.apache.org/jira/browse/OOZIE-1927 OOZIE-1922 MemoryLocksService fails if lock is acquired multiple times in same thread and released https://issues.apache.org/jira/browse/OOZIE-1922 OOZIE-1918 ActionXCommand refactoring for code reuse https://issues.apache.org/jira/browse/OOZIE-1918 OOZIE-1884 ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length 7 https://issues.apache.org/jira/browse/OOZIE-1884 OOZIE-1860 Oozie job mapper launch fails due to null value returned from action file https://issues.apache.org/jira/browse/OOZIE-1860 OOZIE-1855 TestPriorityDelayQueue#testPoll failed intermittently in Jenkins https://issues.apache.org/jira/browse/OOZIE-1855 OOZIE-1829 URIHandlerService doesn't support URI schemes with query strings but no path segment https://issues.apache.org/jira/browse/OOZIE-1829 OOZIE-1816 LogInfo uses action name instead of id https://issues.apache.org/jira/browse/OOZIE-1816 OOZIE-1810 Workflow cannot get into Failed state when kill control node cannot resolve variable in message https://issues.apache.org/jira/browse/OOZIE-1810 OOZIE-1802 Support workflow action log https://issues.apache.org/jira/browse/OOZIE-1802 OOZIE-1793 Improve find bugs reporting for Oozie https://issues.apache.org/jira/browse/OOZIE-1793 OOZIE-1782 Workflow path not found is thrown as SC_UNAUTHORIZED https://issues.apache.org/jira/browse/OOZIE-1782 OOZIE-1779 Add parent-id as a filter option https://issues.apache.org/jira/browse/OOZIE-1779 OOZIE-1705 Enable gc logs and print thread id in logs https://issues.apache.org/jira/browse/OOZIE-1705 OOZIE-1676 Instrumentation and Configuration over the REST API and Web UI should include all Oozie servers https://issues.apache.org/jira/browse/OOZIE-1676 OOZIE-1654 Fix typo (inteval to interval) https://issues.apache.org/jira/browse/OOZIE-1654 OOZIE-1638 Action retry does not respect default retry max count. https://issues.apache.org/jira/browse/OOZIE-1638 OOZIE-1636 OOZIE_SYS table engine should be innodb https://issues.apache.org/jira/browse/OOZIE-1636 OOZIE-1624 Exclusion pattern for sharelib. https://issues.apache.org/jira/browse/OOZIE-1624 OOZIE-1599
[jira] [Commented] (OOZIE-2171) Some error code messages are not parsed correctly due to unescaped single quote
[
https://issues.apache.org/jira/browse/OOZIE-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14364684#comment-14364684
]
Harsh J commented on OOZIE-2171:
+1 again.
Some error code messages are not parsed correctly due to unescaped single
quote
---
Key: OOZIE-2171
URL: https://issues.apache.org/jira/browse/OOZIE-2171
Project: Oozie
Issue Type: Bug
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Attachments: OOZIE-2171.patch, OOZIE-2171.patch
We noticed that the improved whitelist error messages added by OOZIE-2072
weren't being printed properly:
e.g.
{code}
Error: E0901 : E0901: NameNode [localhost:8020] not allowed, not in
Oozies whitelist. Allowed values are: {1}
{code}
Turns out that {{MessageFormat}} requires that single quotes are escaped by
another single quote; otherwise, it:
- doesn't render the single quote
- doesn't parse the \{#\} tokens after the single quote.
For example,
{code}
foo({0} don't have {1}, I, a problem)
{code}
would render as
{code}
I dont have {1}
{code}
We have to replace {{'}} with {{''}} to escape it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2170) Oozie should automatically set configs to make Spark jobs show up in the Spark History Server
[
https://issues.apache.org/jira/browse/OOZIE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366158#comment-14366158
]
Robert Kanter commented on OOZIE-2170:
--
Not sure what happened there; I've kicked off another build.
Oozie should automatically set configs to make Spark jobs show up in the
Spark History Server
-
Key: OOZIE-2170
URL: https://issues.apache.org/jira/browse/OOZIE-2170
Project: Oozie
Issue Type: Improvement
Components: action
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Attachments: OOZIE-2170.patch
If you use yarn-cluster for the Spark action's master, the Spark jobs don't
show up in the Spark History Server or properly link to it from the Spark AM.
The user needs to set this in their Spark action in the workflow.xml:
{code:xml}
spark-opts--conf spark.yarn.historyServer.address=http://SPH18088 --conf
spark.eventLog.dir=hdfs://NN:8020/user/spark/applicationHistory --conf
spark.eventLog.enabled=true/spark-opts
{code}
It would be nice if Oozie did this automatically via some oozie-site.xml
config(s). We could do something similar how the hadoop configs are setup
where it will load a Spark .conf file from a directory based on the RM
specified in the job-tracker.
While we're at it, it might be good to document how to use Spark on YARN:
# Include the spark-assembly jar with your workflow (this is unfortunately
not published in maven)
# Specify yarn-cluster as the master
Also, the Spark example should delete the output dir in {{prepare}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OOZIE-2173) DISCLAIMER.txt still refers to Apache Incubator
Robert Kanter created OOZIE-2173:
Summary: DISCLAIMER.txt still refers to Apache Incubator
Key: OOZIE-2173
URL: https://issues.apache.org/jira/browse/OOZIE-2173
Project: Oozie
Issue Type: Sub-task
Reporter: Robert Kanter
Priority: Minor
In the root of the oozie repo, we have a DISCLAIMER.txt with this:
{quote}
Apache Oozie is an effort undergoing incubation at the Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision-making process
have stabilized in a manner consistent with other successful ASF projects.
While incubation status is not necessarily a reflection of the completeness
or stability of the code, it does indicate that the project has yet to be
fully endorsed by the ASF.
For more information about the incubation status of the Oozie project you
can go to the following page:
http://incubator.apache.org/oozie
{quote}
We've been long out of incubation so this can be deleted. I'm not sure if
something else is supposed to go here now instead; though Hadoop doesn't even
have this file, so it's probably same to just delete it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
Build failed in Jenkins: oozie-trunk-precommit-build #2258
See https://builds.apache.org/job/oozie-trunk-precommit-build/2258/changes Changes: [rkanter] amendment to OOZIE-2171 -- [...truncated 11665 lines...] 148/174 KB 152/174 KB 156/174 KB 160/174 KB 164/174 KB 168/174 KB 172/174 KB 174/174 KB Downloaded: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-archiver/1.0/plexus-archiver-1.0.jar (174 KB at 9611.7 KB/sec) 4/50 KB 8/50 KB 12/50 KB 16/50 KB 20/50 KB 24/50 KB 28/50 KB 32/50 KB 36/50 KB 40/50 KB 44/50 KB 45/50 KB 47/50 KB 50/50 KB Downloaded: http://repo.maven.apache.org/maven2/org/codehaus/plexus/plexus-io/1.0/plexus-io-1.0.jar (50 KB at 439.1 KB/sec) [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/hadooplibs/hadoop-utils-1/target/oozie-hadoop-utils-hadoop-1-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-hadoop-utils --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-hadoop-utils --- [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml [INFO] [INFO] [INFO] Building Apache Oozie Hadoop Distcp hadoop-1-4.2.0-SNAPSHOT hadoop-1-4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-hadoop-distcp --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-hadoop-distcp --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/hadooplibs/hadoop-distcp-1/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-hadoop-distcp --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-hadoop-distcp --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/hadooplibs/hadoop-distcp-1/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-hadoop-distcp --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-hadoop-distcp --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-hadoop-distcp --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/hadooplibs/hadoop-distcp-1/target/oozie-hadoop-distcp-hadoop-1-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-hadoop-distcp --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-hadoop-distcp --- [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml [INFO] [INFO] [INFO] Building Apache Oozie Hadoop Auth hadoop-1-4.2.0-SNAPSHOT hadoop-1-4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-hadoop-auth --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-hadoop-auth --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/hadooplibs/hadoop-auth-1/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-hadoop-auth --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-hadoop-auth --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/hadooplibs/hadoop-auth-1/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-hadoop-auth --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-hadoop-auth --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-hadoop-auth --- [INFO] Building jar:
Build failed in Jenkins: oozie-trunk-precommit-build #2257
See https://builds.apache.org/job/oozie-trunk-precommit-build/2257/changes Changes: [rkanter] OOZIE-2171 Some error code messages are not parsed correctly due to unescaped single quote (rkanter) -- [...truncated 7736 lines...] [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-tools --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools --- [INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml [WARNING] The following patterns were never triggered in this artifact exclusion filter: o '*:*:pom:*' [INFO] Copying files to https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools [WARNING] Assembly file: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment. [INFO] [INFO] [INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-mini --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-mini --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini --- [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml [INFO] [INFO] [INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-distro --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-distro --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-distro --- [INFO] [INFO] --- maven-antrun-plugin:1.6:run (default) @ oozie-distro --- [INFO] Executing tasks main: [mkdir] Created dir: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/downloads [get] Getting:
[jira] [Commented] (OOZIE-2170) Oozie should automatically set configs to make Spark jobs show up in the Spark History Server
[
https://issues.apache.org/jira/browse/OOZIE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366132#comment-14366132
]
Hadoop QA commented on OOZIE-2170:
--
Testing JIRA OOZIE-2170
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 line longer than
132
.{color:green}+1{color} the patch does adds/modifies 2 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} the patch does not seem to introduce new Javadoc
warnings
{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 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} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{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/oozie-trunk-precommit-build/2257/
Oozie should automatically set configs to make Spark jobs show up in the
Spark History Server
-
Key: OOZIE-2170
URL: https://issues.apache.org/jira/browse/OOZIE-2170
Project: Oozie
Issue Type: Improvement
Components: action
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Attachments: OOZIE-2170.patch
If you use yarn-cluster for the Spark action's master, the Spark jobs don't
show up in the Spark History Server or properly link to it from the Spark AM.
The user needs to set this in their Spark action in the workflow.xml:
{code:xml}
spark-opts--conf spark.yarn.historyServer.address=http://SPH18088 --conf
spark.eventLog.dir=hdfs://NN:8020/user/spark/applicationHistory --conf
spark.eventLog.enabled=true/spark-opts
{code}
It would be nice if Oozie did this automatically via some oozie-site.xml
config(s). We could do something similar how the hadoop configs are setup
where it will load a Spark .conf file from a directory based on the RM
specified in the job-tracker.
While we're at it, it might be good to document how to use Spark on YARN:
# Include the spark-assembly jar with your workflow (this is unfortunately
not published in maven)
# Specify yarn-cluster as the master
Also, the Spark example should delete the output dir in {{prepare}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2171) Some error code messages are not parsed correctly due to unescaped single quote
[
https://issues.apache.org/jira/browse/OOZIE-2171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-2171:
-
Attachment: OOZIE-2171-amendment.patch
I had to also commit this amendment patch to fix a trivial issue with the new
tests in {{TestHadoopAccessorService}} on Java 8 (the ordering of HashMaps has
changed).
Some error code messages are not parsed correctly due to unescaped single
quote
---
Key: OOZIE-2171
URL: https://issues.apache.org/jira/browse/OOZIE-2171
Project: Oozie
Issue Type: Bug
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Fix For: trunk
Attachments: OOZIE-2171-amendment.patch, OOZIE-2171.patch,
OOZIE-2171.patch
We noticed that the improved whitelist error messages added by OOZIE-2072
weren't being printed properly:
e.g.
{code}
Error: E0901 : E0901: NameNode [localhost:8020] not allowed, not in
Oozies whitelist. Allowed values are: {1}
{code}
Turns out that {{MessageFormat}} requires that single quotes are escaped by
another single quote; otherwise, it:
- doesn't render the single quote
- doesn't parse the \{#\} tokens after the single quote.
For example,
{code}
foo({0} don't have {1}, I, a problem)
{code}
would render as
{code}
I dont have {1}
{code}
We have to replace {{'}} with {{''}} to escape it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (OOZIE-2170) Oozie should automatically set configs to make Spark jobs show up in the Spark History Server
[
https://issues.apache.org/jira/browse/OOZIE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366183#comment-14366183
]
Hadoop QA commented on OOZIE-2170:
--
Testing JIRA OOZIE-2170
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 line longer than
132
.{color:green}+1{color} the patch does adds/modifies 2 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} the patch does not seem to introduce new Javadoc
warnings
{color:red}-1 COMPILE{color}
.{color:red}-1{color} HEAD does not compile
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{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} - patch does not compile, cannot run testcases
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch
{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/oozie-trunk-precommit-build/2258/
Oozie should automatically set configs to make Spark jobs show up in the
Spark History Server
-
Key: OOZIE-2170
URL: https://issues.apache.org/jira/browse/OOZIE-2170
Project: Oozie
Issue Type: Improvement
Components: action
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Attachments: OOZIE-2170.patch
If you use yarn-cluster for the Spark action's master, the Spark jobs don't
show up in the Spark History Server or properly link to it from the Spark AM.
The user needs to set this in their Spark action in the workflow.xml:
{code:xml}
spark-opts--conf spark.yarn.historyServer.address=http://SPH18088 --conf
spark.eventLog.dir=hdfs://NN:8020/user/spark/applicationHistory --conf
spark.eventLog.enabled=true/spark-opts
{code}
It would be nice if Oozie did this automatically via some oozie-site.xml
config(s). We could do something similar how the hadoop configs are setup
where it will load a Spark .conf file from a directory based on the RM
specified in the job-tracker.
While we're at it, it might be good to document how to use Spark on YARN:
# Include the spark-assembly jar with your workflow (this is unfortunately
not published in maven)
# Specify yarn-cluster as the master
Also, the Spark example should delete the output dir in {{prepare}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-2172) ZooKeeper Security Tests failed with JVM IBM JAVA
[ https://issues.apache.org/jira/browse/OOZIE-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Kanter updated OOZIE-2172: - Component/s: HA ZooKeeper Security Tests failed with JVM IBM JAVA - Key: OOZIE-2172 URL: https://issues.apache.org/jira/browse/OOZIE-2172 Project: Oozie Issue Type: Test Components: HA Affects Versions: 4.1.0 Environment: zookeeper-security-tests]# mvn -verion Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T12:29:23-05:00) Maven home: /opt/apache-maven-3.2.5 Java version: 1.7.0, vendor: IBM Corporation Java home: /usr/lib/jvm/ibm-java-x86_64-71-pxa6470_27sr2fp10-20141218_02/jre Default locale: en_US, platform encoding: ISO-8859-1 OS name: linux, version: 3.10.0-229.el7.x86_64, arch: amd64, family: unix Reporter: pascal oliva ZooKeeper Security Tests failed by using IBM JAVA --- Concurrency config is parallel='classes', perCoreThreadCount=false, threadCount=1, useUnlimitedThreads=false Running org.apache.oozie.util.TestZKUtilsWithSecurity Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 36.493 sec FAILURE! Results : Tests in error: testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): org.apache.hcatalog.common.HCatException : 9001 : Exception occurred while processing HCat request : MetaException while creating HMS client. Cause : MetaException(message:Could not connect to meta store using any of the URIs provided. Most recent failure: org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection refused(..) testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): Could not configure server because SASL configuration did not allow the ZooKeeper server to authenticate itself properly: javax.security.auth.login.LoginException: Bad JAAS configuration: unrecognized option: storeKey .. Traces On target/./surefire-reports/org.apache.oozie.util.TestZKUtilsWithSecurity-output.txt at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at org.apache.hcatalog.common.HiveClientCache.getOrCreate(HiveClientCache.java:167) at org.apache.hcatalog.common.HiveClientCache.get(HiveClientCache.java:143) at org.apache.hcatalog.common.HCatUtil.getHiveClient(HCatUtil.java:548) at org.apache.hcatalog.api.HCatClientHMSImpl.initialize(HCatClientHMSImpl.java:596) ... 27 more testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity) Time elapsed: 0.009 sec ERROR! java.io.IOException: Could not configure server because SASL configuration did not allow the ZooKeeper server to authenticate itself properly: javax.security.auth.login.LoginException: Bad JAAS configuration: unrecognized option: storeKey at org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:207) at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87) at org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:111) at org.apache.curator.test.TestingZooKeeperMain.runFromConfig(TestingZooKeeperMain.java:73) at org.apache.curator.test.TestingZooKeeperServer$1.run(TestingZooKeeperServer.java:134) at java.lang.Thread.run(Thread.java:863) ... howto reproduce : git clone -b branch-4.1 https://github.com/apache/oozie.git cd oozie ./bin/mkdistro.sh -DskipTests -Phadoop-2 cd zookeeper-security-tests/ mvn clean test -Phadoop-2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (OOZIE-1624) Exclusion pattern for sharelib.
[ https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366416#comment-14366416 ] Purshotam Shah commented on OOZIE-1624: --- We had an incidence where bug in launcher sharelib was causing job failure. We had to issue new release to fix the issue. With exclusion list we could have provided workaround to user. Exclusion pattern for sharelib. --- Key: OOZIE-1624 URL: https://issues.apache.org/jira/browse/OOZIE-1624 Project: Oozie Issue Type: Sub-task Reporter: Purshotam Shah Assignee: Purshotam Shah Attachments: OOZIE-1624-V2.patch, OOZIE-1624-v1.patch Sharelib may bring some jar which might conflict with user jars. Ex. Sharelib hive has json-2..jar, where as some of the user use-case need higher version of json jar. He should be able to exclude sharelib json jar and bring his own version. property nameoozie.action.sharelib.for.hive.exclusion/name valuejson-\*.jar|abc-*.jar/value /property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Build failed in Jenkins: oozie-trunk-precommit-build #2259
See https://builds.apache.org/job/oozie-trunk-precommit-build/2259/ -- [...truncated 7887 lines...] [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-tools --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-tools --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools --- [INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml [WARNING] The following patterns were never triggered in this artifact exclusion filter: o '*:*:pom:*' [INFO] Copying files to https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools [WARNING] Assembly file: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/tools/target/oozie-tools-4.2.0-SNAPSHOT-tools is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment. [INFO] [INFO] [INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-mini --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 3 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-mini --- [INFO] Nothing to compile - all classes are up to date [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/minitest/target/oozie-mini-4.2.0-SNAPSHOT.jar [INFO] [INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ oozie-mini --- [INFO] [INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini --- [INFO] Reading assembly descriptor: src/main/assemblies/empty.xml [INFO] [INFO] [INFO] Building Apache Oozie Distro 4.2.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ oozie-distro --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ oozie-distro --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/src/test/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ oozie-distro --- [INFO] No sources to compile [INFO] [INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro --- [INFO] Tests are skipped. [INFO] [INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro --- [INFO] Building jar: https://builds.apache.org/job/oozie-trunk-precommit-build/ws/distro/target/oozie-distro-4.2.0-SNAPSHOT.jar [INFO] [INFO] ---
[jira] [Commented] (OOZIE-1624) Exclusion pattern for sharelib.
[
https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14366489#comment-14366489
]
Hadoop QA commented on OOZIE-1624:
--
Testing JIRA OOZIE-1624
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:green}+1{color} the patch does not introduce any trailing spaces
.{color:red}-1{color} the patch contains 1 line(s) longer than 132
characters
.{color:green}+1{color} the patch does 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} the patch does not seem to introduce new Javadoc
warnings
{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 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} - patch does not compile, cannot run testcases
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch
{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/oozie-trunk-precommit-build/2259/
Exclusion pattern for sharelib.
---
Key: OOZIE-1624
URL: https://issues.apache.org/jira/browse/OOZIE-1624
Project: Oozie
Issue Type: Sub-task
Reporter: Purshotam Shah
Assignee: Purshotam Shah
Attachments: OOZIE-1624-V2.patch, OOZIE-1624-v1.patch
Sharelib may bring some jar which might conflict with user jars.
Ex. Sharelib hive has json-2..jar, where as some of the user use-case
need higher version of json jar.
He should be able to exclude sharelib json jar and bring his own version.
property
nameoozie.action.sharelib.for.hive.exclusion/name
valuejson-\*.jar|abc-*.jar/value
/property
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OOZIE-1624) Exclusion pattern for sharelib.
[ https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah updated OOZIE-1624: -- Attachment: OOZIE-1624-V2.patch Exclusion pattern for sharelib. --- Key: OOZIE-1624 URL: https://issues.apache.org/jira/browse/OOZIE-1624 Project: Oozie Issue Type: Sub-task Reporter: Purshotam Shah Assignee: Purshotam Shah Attachments: OOZIE-1624-V2.patch, OOZIE-1624-v1.patch Sharelib may bring some jar which might conflict with user jars. Ex. Sharelib hive has json-2..jar, where as some of the user use-case need higher version of json jar. He should be able to exclude sharelib json jar and bring his own version. property nameoozie.action.sharelib.for.hive.exclusion/name valuejson-\*.jar|abc-*.jar/value /property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-1624) Exclusion pattern for sharelib.
[ https://issues.apache.org/jira/browse/OOZIE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Purshotam Shah updated OOZIE-1624: -- Description: Sharelib may bring some jar which might conflict with user jars. Ex. Sharelib hive has json-2..jar, where as some of the user use-case need higher version of json jar. He should be able to exclude sharelib json jar and bring his own version. property nameoozie.action.sharelib.for.hive.exclusion/name valuejson-\*.jar|abc-*.jar/value /property was: Sharelib may bring some jar which might conflict with user jars. Ex. Sharelib hive has json-2..jar, where as some of the user use-case need higher version of json jar. He should be able to exclude sharelib json jar and bring his own version. property nameoozie.action.sharelib.for.hive.exclusion/name valuejson-\*.jar,abc-*.jar/value /property Exclusion pattern for sharelib. --- Key: OOZIE-1624 URL: https://issues.apache.org/jira/browse/OOZIE-1624 Project: Oozie Issue Type: Sub-task Reporter: Purshotam Shah Assignee: Purshotam Shah Attachments: OOZIE-1624-v1.patch Sharelib may bring some jar which might conflict with user jars. Ex. Sharelib hive has json-2..jar, where as some of the user use-case need higher version of json jar. He should be able to exclude sharelib json jar and bring his own version. property nameoozie.action.sharelib.for.hive.exclusion/name valuejson-\*.jar|abc-*.jar/value /property -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OOZIE-2170) Oozie should automatically set configs to make Spark jobs show up in the Spark History Server
[
https://issues.apache.org/jira/browse/OOZIE-2170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Kanter updated OOZIE-2170:
-
Attachment: OOZIE-2170.patch
The patch adds a new {{SparkConfigurationService}} which will load the
spark-defaults.conf files defined by the new
{{oozie.service.SparkConfigurationService.spark.configurations}} oozie-site
property. It operates similarly to how we load Hadoop conf and default action
confs
When the master starts with yarn and the {{job-tracker}} matches something
in {{oozie.service.SparkConfigurationService.spark.configurations}}, Oozie will
inject the properties from spark-defaults.conf as {{--conf}} parameters in the
{{spark-opts}} field.
In addition to the unit tests, I also tested out a variety of scenarios
manually in a cluster (configs defined, invalid configs, {{*}}, duplicate
properties, etc).
Oozie should automatically set configs to make Spark jobs show up in the
Spark History Server
-
Key: OOZIE-2170
URL: https://issues.apache.org/jira/browse/OOZIE-2170
Project: Oozie
Issue Type: Improvement
Components: action
Affects Versions: trunk
Reporter: Robert Kanter
Assignee: Robert Kanter
Attachments: OOZIE-2170.patch
If you use yarn-cluster for the Spark action's master, the Spark jobs don't
show up in the Spark History Server or properly link to it from the Spark AM.
The user needs to set this in their Spark action in the workflow.xml:
{code:xml}
spark-opts--conf spark.yarn.historyServer.address=http://SPH18088 --conf
spark.eventLog.dir=hdfs://NN:8020/user/spark/applicationHistory --conf
spark.eventLog.enabled=true/spark-opts
{code}
It would be nice if Oozie did this automatically via some oozie-site.xml
config(s). We could do something similar how the hadoop configs are setup
where it will load a Spark .conf file from a directory based on the RM
specified in the job-tracker.
While we're at it, it might be good to document how to use Spark on YARN:
# Include the spark-assembly jar with your workflow (this is unfortunately
not published in maven)
# Specify yarn-cluster as the master
Also, the Spark example should delete the output dir in {{prepare}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (OOZIE-2172) ZooKeeper Security Tests failed with JVM IBM JAVA
pascal oliva created OOZIE-2172: --- Summary: ZooKeeper Security Tests failed with JVM IBM JAVA Key: OOZIE-2172 URL: https://issues.apache.org/jira/browse/OOZIE-2172 Project: Oozie Issue Type: Test Affects Versions: 4.1.0 Environment: zookeeper-security-tests]# mvn -verion Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1; 2014-12-14T12:29:23-05:00) Maven home: /opt/apache-maven-3.2.5 Java version: 1.7.0, vendor: IBM Corporation Java home: /usr/lib/jvm/ibm-java-x86_64-71-pxa6470_27sr2fp10-20141218_02/jre Default locale: en_US, platform encoding: ISO-8859-1 OS name: linux, version: 3.10.0-229.el7.x86_64, arch: amd64, family: unix Reporter: pascal oliva ZooKeeper Security Tests failed by using IBM JAVA --- Concurrency config is parallel='classes', perCoreThreadCount=false, threadCount=1, useUnlimitedThreads=false Running org.apache.oozie.util.TestZKUtilsWithSecurity Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 36.493 sec FAILURE! Results : Tests in error: testCheckAndSetACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): org.apache.hcatalog.common.HCatException : 9001 : Exception occurred while processing HCat request : MetaException while creating HMS client. Cause : MetaException(message:Could not connect to meta store using any of the URIs provided. Most recent failure: org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection refused(..) testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity): Could not configure server because SASL configuration did not allow the ZooKeeper server to authenticate itself properly: javax.security.auth.login.LoginException: Bad JAAS configuration: unrecognized option: storeKey .. Traces On target/./surefire-reports/org.apache.oozie.util.TestZKUtilsWithSecurity-output.txt at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at org.apache.hcatalog.common.HiveClientCache.getOrCreate(HiveClientCache.java:167) at org.apache.hcatalog.common.HiveClientCache.get(HiveClientCache.java:143) at org.apache.hcatalog.common.HCatUtil.getHiveClient(HCatUtil.java:548) at org.apache.hcatalog.api.HCatClientHMSImpl.initialize(HCatClientHMSImpl.java:596) ... 27 more testNewUsingACLs(org.apache.oozie.util.TestZKUtilsWithSecurity) Time elapsed: 0.009 sec ERROR! java.io.IOException: Could not configure server because SASL configuration did not allow the ZooKeeper server to authenticate itself properly: javax.security.auth.login.LoginException: Bad JAAS configuration: unrecognized option: storeKey at org.apache.zookeeper.server.ServerCnxnFactory.configureSaslLogin(ServerCnxnFactory.java:207) at org.apache.zookeeper.server.NIOServerCnxnFactory.configure(NIOServerCnxnFactory.java:87) at org.apache.zookeeper.server.ZooKeeperServerMain.runFromConfig(ZooKeeperServerMain.java:111) at org.apache.curator.test.TestingZooKeeperMain.runFromConfig(TestingZooKeeperMain.java:73) at org.apache.curator.test.TestingZooKeeperServer$1.run(TestingZooKeeperServer.java:134) at java.lang.Thread.run(Thread.java:863) ... howto reproduce : git clone -b branch-4.1 https://github.com/apache/oozie.git cd oozie ./bin/mkdistro.sh -DskipTests -Phadoop-2 cd zookeeper-security-tests/ mvn clean test -Phadoop-2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
