date:20191128

[jira] Subscription: Oozie Patch Available

2019-11-28 Thread jira

Issue Subscription
Filter: Oozie Patch Available (92 issues)

Subscriber: ooziedaily

Key Summary
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-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
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

Re: [VOTE] Release Oozie 5.2.0 (candidate 0)

2019-11-28 Thread Julia Kinga Marton

Hi all,

+1, from my side.

I did the following steps:
- checked sha
- checked gpg
- checked rat report
- built Oozie with Hadoop 2.6.0 using mkdistro
- tested some basic cli commands and run the examples in pseudo distributed
mode. Found two small issue related the Hive example (OOZIE-3563

- OOZIE-3562 ), but since
we are using a very old version of Hive, I don't consider them blockers.

Regards,
Kinga

On Mon, Nov 25, 2019 at 10:55 AM Peter Bacsko 
wrote:

> Hi all,
>
> I did the following:
> 1. Downloaded the package
> 2. Built the distro with tests (didn't see failures) under Ubuntu 18.04,
> JDK8
> 3. Integrated Oozie with 3-node Hadoop cluster running version 2.9.2
> 4. Run the MapReduce example
>
> I didn't have much time to do anything else.
>
> I'm giving a +1 regardless, but would like to see results from additional
> people to have more confidence.
>
> Regards,
> Peter
>
> On Mon, Nov 25, 2019 at 9:55 AM Andras Salamon
>  wrote:
>
> > Hi All,
> >
> > We still have only one vote (+1), so I extend the voting period again.
> > Please cast your vote till Dec 1st.
> >
> > Best,
> > Sala
> >
> > On Mon, Nov 18, 2019 at 10:41 AM Andras Salamon 
> > wrote:
> >
> > > Hi All,
> > >
> > > We only have one vote so far (+1), so I extend the voting till Nov
> 24th.
> > > Please test 5.2.0 RC0 if you have time.
> > >
> > > Best,
> > > Sala
> > >
> > > On Thu, Nov 14, 2019 at 3:32 PM Peter Cseh
>  > >
> > > wrote:
> > >
> > >> Andras, thanks for building the RC and the summary!
> > >> I don't think that the Java 11 issues are a problem, especially if it
> > >> works
> > >> when compiling with a different Hadoop.
> > >>
> > >> The checksums and signatures are good.
> > >> I've used Jdk8u212 on my mac to build the distro.
> > >> Distro creation succeeded with all tests passing:
> > >>  ./bin/mkdistro.sh  -Dtest.timeout=7200 -Doozie.test.waitfor.ratio=3
> > >> -Dsurefire.rerunFailingTestsCount=3
> > >> [INFO]
> > >>
> 
> > >> [INFO] Reactor Summary for Apache Oozie Main 5.2.0:
> > >> [INFO]
> > >> [INFO] Apache Oozie Main .. SUCCESS [
> > >>  1.538 s]
> > >> [INFO] Apache Oozie Fluent Job  SUCCESS [
> > >>  0.082 s]
> > >> [INFO] Apache Oozie Fluent Job API  SUCCESS [
> > >> 13.131 s]
> > >> [INFO] Apache Oozie Client  SUCCESS [
> > >> 10.897 s]
> > >> [INFO] Apache Oozie Share Lib Oozie ... SUCCESS [
> > >>  6.554 s]
> > >> [INFO] Apache Oozie Share Lib HCatalog  SUCCESS [
> > >>  3.479 s]
> > >> [INFO] Apache Oozie Share Lib Distcp .. SUCCESS [
> > >>  0.388 s]
> > >> [INFO] Apache Oozie Core .. SUCCESS [
> > >>  01:27 h]
> > >> [INFO] Apache Oozie Share Lib Streaming ... SUCCESS
> > [12:50
> > >> min]
> > >> [INFO] Apache Oozie Share Lib Pig . SUCCESS
> > [05:38
> > >> min]
> > >> [INFO] Apache Oozie Share Lib Git . SUCCESS [
> > >> 59.980 s]
> > >> [INFO] Apache Oozie Share Lib Hive  SUCCESS
> > [02:41
> > >> min]
> > >> [INFO] Apache Oozie Share Lib Hive 2 .. SUCCESS
> > [02:20
> > >> min]
> > >> [INFO] Apache Oozie Share Lib Sqoop ... SUCCESS
> > [05:14
> > >> min]
> > >> [INFO] Apache Oozie Examples .. SUCCESS [
> > >> 33.237 s]
> > >> [INFO] Apache Oozie Share Lib Spark ... SUCCESS
> > [02:10
> > >> min]
> > >> [INFO] Apache Oozie Share Lib . SUCCESS [
> > >> 16.819 s]
> > >> [INFO] Apache Oozie Docs .. SUCCESS [
> > >>  0.388 s]
> > >> [INFO] Apache Oozie WebApp  SUCCESS [
> > >>  4.631 s]
> > >> [INFO] Apache Oozie Tools . SUCCESS [
> > >> 47.751 s]
> > >> [INFO] Apache Oozie MiniOozie . SUCCESS [
> > >> 56.070 s]
> > >> [INFO] Apache Oozie Fluent Job Client . SUCCESS [
> > >> 48.696 s]
> > >> [INFO] Apache Oozie Server  SUCCESS [
> > >>  5.554 s]
> > >> [INFO] Apache Oozie Distro  SUCCESS [
> > >> 39.502 s]
> > >> [INFO] Apache Oozie ZooKeeper Security Tests .. SUCCESS [
> > >> 47.454 s]
> > >> [INFO]
> > >>
> 
> > >> [INFO] BUILD SUCCESS
> > >> [INFO]
> > >>
> 
> > >> [INFO] Total time:  02:05 h
> > >> [INFO] Finished at: 2019-11-14T14:46:01+01:00
> > >> [INFO]
> > >>
> 
> > >>
> > >> Oozie distro

[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords

2019-11-28 Thread ASF subversion and git services (Jira)



[ 
https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984321#comment-16984321
 ] 

ASF subversion and git services commented on OOZIE-3549:


Commit 31caabc2ad73e2f7ff5e077e760483964a7b9cca in oozie's branch 
refs/heads/master from Andras Salamon
[ https://gitbox.apache.org/repos/asf?p=oozie.git;h=31caabc ]

OOZIE-3549 Add back support for truststore passwords (matijhs via asalamon74)


> 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-v3.patch, 
> OOZIE-3549-v4.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-3562) Fix Hive example

2019-11-28 Thread Mate Juhasz (Jira)



[ 
https://issues.apache.org/jira/browse/OOZIE-3562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984312#comment-16984312
 ] 

Mate Juhasz commented on OOZIE-3562:


[~kmarton] could you share some info about the env where it is failing? I could 
see this with Java 11, so I suspected Java 8+ is not yet supported by the Hive 
version we use upstream

> Fix Hive example
> 
>
> Key: OOZIE-3562
> URL: https://issues.apache.org/jira/browse/OOZIE-3562
> Project: Oozie
>  Issue Type: Bug
>  Components: examples
>Affects Versions: 5.1.0
>Reporter: Kinga Marton
>Priority: Major
> Attachments: hive1StachTrace.txt
>
>
> Hive example in pseudo distributed mode is failing with the following error 
> message:
> {code:java}
> ACTION[008-191121145732587-oozie-mart-W@hive-node] Launcher exception: 
> java.lang.RuntimeException: Unable to instantiate 
> org.apache.hadoop.hive.ql.metadata.SessionHiveMetaStoreClient
> {code}
> See the full stacktrace attached.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords

2019-11-28 Thread Hadoop QA (Jira)



[ 
https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984304#comment-16984304
 ] 

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: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 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} 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:green}+1 TESTS{color}
.Tests run: 3199
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
.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:green}*+1 Overall result, good!, no -1s*{color}


The full output of the test-patch run is available at

. https://builds.apache.org/job/PreCommit-OOZIE-Build/1259/



> 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-v3.patch, 
> OOZIE-3549-v4.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)

Failed: OOZIE-3549 PreCommit Build #1259

2019-11-28 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3549
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1259/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 2.15 MB...]
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [client].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [examples].
[TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts
[DEBUG] There are no new bugs found in [webapp].
[INFO] There are no new bugs found totally].
[TRACE] SpotBugs diffs checked and reports created
[TRACE] Summary file size is 2535 bytes
[TRACE] Full summary file size is 1525 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-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 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 2 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: 3199
Tests failed at first run:
TestCoordActionInputCheckXCommandNonUTC>TestCoordActionInputCheckXCommand#testNone
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, good!, no -1s


The full output of the test-patch run is available at

 https://builds.apache.org/job/PreCommit-OOZIE-Build/1259/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  34200 0  100  3420  0   2312  0:00:01  0:00:01 --:--:--

[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords

2019-11-28 Thread Hadoop QA (Jira)



[ 
https://issues.apache.org/jira/browse/OOZIE-3549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16984228#comment-16984228
 ] 

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-v3.patch, 
> OOZIE-3549-v4.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

2019-11-28 Thread Mate Juhasz (Jira)



 [ 
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-v4.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-v3.patch, 
> OOZIE-3549-v4.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] Subscription: Oozie Patch Available

Re: [VOTE] Release Oozie 5.2.0 (candidate 0)

[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords

[jira] [Commented] (OOZIE-3562) Fix Hive example

[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords

Failed: OOZIE-3549 PreCommit Build #1259

[jira] [Commented] (OOZIE-3549) Add back support for truststore passwords

[jira] [Updated] (OOZIE-3549) Add back support for truststore passwords

8 matches

Site Navigation

Mail list logo

Footer information