date:20161006

[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0

2016-10-06 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna commented on OOZIE-2613:
---

The directory structure for the partitions are created in the 
{{MiniHCatServer#createPartitionDir}} method. I replaced the code with below 
but it is still giving the same error.

{code}
public String createPartitionDir(String db, String table, String 
partitionSpec, String dbLocation) throws Exception {
FileSystem.get(hadoopConf).mkdirs(new Path(dbLocation), 
FsPermission.valueOf("-rwxrwxrwx"));
FileSystem.get(hadoopConf).setOwner(new Path(dbLocation), "test", 
"test");
String dir = getPartitionDir(db, table, partitionSpec, dbLocation);
FileSystem.get(hadoopConf).mkdirs(new Path(dir), 
FsPermission.valueOf("-rwxrwxrwx"));
FileSystem.get(hadoopConf).setOwner(new Path(dir), "test", "test");
return dir;
}
{code}

> Upgrade hive version from 0.13.1 to 1.2.0
> -
>
> Key: OOZIE-2613
> URL: https://issues.apache.org/jira/browse/OOZIE-2613
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Reporter: Abhishek Bafna
>Assignee: Abhishek Bafna
>Priority: Blocker
> Fix For: 4.3.0
>
> Attachments: OOZIE-2613-00.patch, OOZIE-2613-01.patch, 
> OOZIE-2613-02.patch, OOZIE-2613-03.patch, OOZIE-2613-05.patch, 
> OOZIE-2613-06.patch, OOZIE-2613-07.patch, OOZIE-2613-08.patch, 
> OOZIE-2613-09.patch
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1814) Oozie should mask any passwords in logs and REST interfaces

2016-10-06 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-1814:
-

The build breaks because of a flaky test.

> Oozie should mask any passwords in logs and REST interfaces
> ---
>
> Key: OOZIE-1814
> URL: https://issues.apache.org/jira/browse/OOZIE-1814
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Bowen Zhang
>Assignee: Andras Piros
>  Labels: newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1814.002.patch, OOZIE-1814.003.patch, 
> OOZIE-1814.004.patch, OOZIE-1814.005.patch, OOZIE-1814.006.patch, 
> OOZIE-1814.007.patch, oozie-1814.patch
>
>
> Following passwords are currently visible in the instrumentation log, REST 
> endpoints, WebUI, and CLI (WebUI and CLI simply call the REST endpoints):
> * {{javax.net.ssl.trustStorePassword}}
> * {{oozie.https.keystore.pass}}
> * {{HADOOP_CREDSTORE_PASSWORD}}
> * {{OOZIE_HTTPS_KEYSTORE_PASSWORD}}
> * {{OOZIE_HTTPS_TRUSTSTORE_PASSWORD}}
> There are a few examples that illustrate password leakage.
> {noformat}
> # grep -i pass /var/log/oozie/oozie-instrumentation.log
> OOZIE_HTTPS_TRUSTSTORE_PASSWORD = password
> javax.net.ssl.trustStorePassword = password
> oozie.https.keystore.pass = password
> HADOOP_CREDSTORE_PASSWORD = password
> OOZIE_HTTPS_KEYSTORE_PASSWORD = password
> CATALINA_OPTS = -Xms603979776 -Xmx603979776 
> -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/tmp/OOZIE-1_OOZIE-1-OOZIE_SERVER-2e75cc1293d9058eef7250a18f347c43_pid30867.hprof
>  -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh 
> -Doozie.home.dir=/usr/lib/oozie 
> -Doozie.config.dir=/var/run/cloudera-scm-agent/process/320-oozie-OOZIE_SERVER 
> -Doozie.log.dir=/var/log/oozie 
> -Doozie.log.file=oozie-cmf-OOZIE-1-OOZIE_SERVER-nightly-1.gce.cloudera.com.log.out
>  -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=log4j.properties 
> -Doozie.log4j.reload=10 -Doozie.http.hostname=nightly-1.gce.cloudera.com 
> -Doozie.http.port=11000 -Djava.net.preferIPv4Stack=true 
> -Doozie.admin.port=11001 -Dderby.stream.error.file=/var/log/oozie/derby.log 
> -Doozie.instance.id=nightly-1.gce.cloudera.com 
> -Djava.library.path=/usr/lib/hadoop/lib/native -Doozie.https.port=11443 
> -Djavax.net.ssl.trustStore=/etc/cdep-ssl-conf/CA_STANDARD/truststore.jks 
> -Djavax.net.ssl.trustStorePassword=password
> {noformat}
> Oozie dumps the env vars and Java sys props to the instrumentation log on 
> startup.
> {noformat}
> # curl --negotiate -u foo:bar -k 
> https://nightly-1.gce.cloudera.com:11443/oozie/v2/admin/os-env | python -m 
> json.tool | grep -i pass
> "CATALINA_OPTS": "-Xms603979776 -Xmx603979776 -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/tmp/OOZIE-1_OOZIE-1-OOZIE_SERVER-2e75cc1293d9058eef7250a18f347c43_pid30867.hprof
>  -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh 
> -Doozie.home.dir=/usr/lib/oozie 
> -Doozie.config.dir=/var/run/cloudera-scm-agent/process/320-oozie-OOZIE_SERVER 
> -Doozie.log.dir=/var/log/oozie 
> -Doozie.log.file=oozie-cmf-OOZIE-1-OOZIE_SERVER-nightly-1.gce.cloudera.com.log.out
>  -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=log4j.properties 
> -Doozie.log4j.reload=10 -Doozie.http.hostname=nightly-1.gce.cloudera.com 
> -Doozie.http.port=11000 -Djava.net.preferIPv4Stack=true 
> -Doozie.admin.port=11001 -Dderby.stream.error.file=/var/log/oozie/derby.log 
> -Doozie.instance.id=nightly-1.gce.cloudera.com 
> -Djava.library.path=/usr/lib/hadoop/lib/native -Doozie.https.port=11443 
> -Djavax.net.ssl.trustStore=/etc/cdep-ssl-conf/CA_STANDARD/truststore.jks 
> -Djavax.net.ssl.trustStorePassword=password ",
> "HADOOP_CREDSTORE_PASSWORD": "password",
> "OOZIE_HTTPS_KEYSTORE_PASSWORD": "password",
> "OOZIE_HTTPS_TRUSTSTORE_PASSWORD": "password",
> {noformat}
> {noformat}
> # curl --negotiate -u foo:bar -k 
> https://nightly-1.gce.cloudera.com:11443/oozie/v2/admin/java-sys-properties | 
> python -m json.tool | grep -i pass
> "javax.net.ssl.trustStorePassword": "password",
> "oozie.https.keystore.pass": "password",
> {noformat}
> The REST API has two endpoints, {{admin/os-env}} and 
> {{admin/java-sys-properties}}, which are also available in the Web UI and 
> CLI.  These expose the env vars and Java sys props too.
> We should mask these like we do for the configuration endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2393) Allow table drop in hcat prepare

2016-10-06 Thread Abhishek Bafna (JIRA)


 [ 
https://issues.apache.org/jira/browse/OOZIE-2393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Abhishek Bafna updated OOZIE-2393:
--
Attachment: OOZIE-2393-01.patch

> Allow table drop in hcat prepare
> 
>
> Key: OOZIE-2393
> URL: https://issues.apache.org/jira/browse/OOZIE-2393
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Muhammad Ehsan ul Haque
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: hcatalog, prepare
> Fix For: 5.0.0
>
> Attachments: OOZIE-2393-00.patch, OOZIE-2393-01.patch
>
>
> The hcat prepare only allows to drop partitions. It would be nice to also 
> allow dropping of table, depending on the URL. The current format of the URL 
> is
> {code}hcat://[metastore server]:[port]/[database name]/[table 
> name]/[partkey1]=[value];[partkey2]=[value]{code}
> where at least one partition must be provided, otherwise the prepare step 
> fails with the fololwing exception.
> {code}
> Starting the execution of prepare actions
> Creating HCatClient for user=ehsan.haq (auth:SIMPLE) and 
> server=thrift://datavault-prod-app2.internal.machines:9083
> Prepare execution in the Launcher Mapper has failed
> Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), Error 
> trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> org.apache.oozie.action.hadoop.LauncherException: Error trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:178)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:450)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: org.apache.oozie.action.hadoop.LauncherException: Error trying to 
> drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:64)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.execute(PrepareActionsDriver.java:89)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.doOperations(PrepareActionsDriver.java:67)
> at 
> org.apache.oozie.action.hadoop.LauncherMapper.executePrepare(LauncherMapper.java:446)
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:174)
> ... 8 more
> Caused by: java.net.URISyntaxException: URI path is not in expected format: 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.util.HCatURI.parse(HCatURI.java:66)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:52)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:48)
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:52)
> ... 12 more
> Oozie Launcher failed, finishing Hadoop job gracefully
> {code}
> h3. Suggestion
> In the URL if the partition is not provided then it should delete the entire 
> table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 52519: Allow table drop in hcat prepare

2016-10-06 Thread Abhishek Bafna


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52519/
---

(Updated Oct. 6, 2016, 1:32 p.m.)


Review request for oozie.


Bugs: OOZIE-2393
https://issues.apache.org/jira/browse/OOZIE-2393


Repository: oozie-git


Description
---

Allow table drop in hcat prepare


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/dependency/HCatURIHandler.java 67b37ec 
  core/src/test/java/org/apache/oozie/action/hadoop/TestFsActionExecutor.java 
5345ae6 
  
core/src/test/java/org/apache/oozie/action/hadoop/TestLauncherHCatURIHandler.java
 66d4ecc 
  core/src/test/java/org/apache/oozie/coord/TestHCatELFunctions.java e1cf133 
  core/src/test/java/org/apache/oozie/dependency/TestHCatURIHandler.java 
a49eba5 
  core/src/test/java/org/apache/oozie/test/MiniHCatServer.java 8699ff8 
  core/src/test/java/org/apache/oozie/test/XHCatTestCase.java 2adbee7 
  docs/src/site/twiki/DG_HCatalogIntegration.twiki fd6bcb6 
  docs/src/site/twiki/WorkflowFunctionalSpec.twiki 7474ea5 
  
sharelib/hcatalog/src/main/java/org/apache/oozie/action/hadoop/HCatLauncherURIHandler.java
 6798768 
  sharelib/hcatalog/src/main/java/org/apache/oozie/util/HCatURI.java 8ec3fae 
  sharelib/hcatalog/src/test/java/org/apache/oozie/util/TestHCatURI.java 
1b1a8fa 

Diff: https://reviews.apache.org/r/52519/diff/


Testing
---


Thanks,

Abhishek Bafna

Build failed in Jenkins: oozie-trunk-find-patches-available #135445

2016-10-06 Thread Apache Jenkins Server

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision b24477a3ee8c12f268a1edc084fe1abb8cec5d97 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f b24477a3ee8c12f268a1edc084fe1abb8cec5d97
 > git rev-list b24477a3ee8c12f268a1edc084fe1abb8cec5d97 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson3635489647906646721.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100  210k0  210k0 0   277k  0 --:--:-- --:--:-- --:--:--  277k
100  448k0  448k0 0   263k  0 --:--:--  0:00:01 --:--:--  263k
100  808k0  808k0 0   292k  0 --:--:--  0:00:02 --:--:--  292k
100 1160k0 1160k0 0   309k  0 --:--:--  0:00:03 --:--:--  309k
100 1474k0 1474k0 0   308k  0 --:--:--  0:00:04 --:--:--  308k
100 1711k0 1711k0 0   309k  0 --:--:--  0:00:05 --:--:--  315k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #135446

2016-10-06 Thread Apache Jenkins Server

See

Jenkins build is back to normal : oozie-trunk-precommit-build #3359

2016-10-06 Thread Apache Jenkins Server

See

[jira] [Commented] (OOZIE-2393) Allow table drop in hcat prepare

2016-10-06 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2393:
--

Testing JIRA OOZIE-2393

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 7 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:green}+1 TESTS{color}
.Tests run: 1818
{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{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/oozie-trunk-precommit-build/3359/

> Allow table drop in hcat prepare
> 
>
> Key: OOZIE-2393
> URL: https://issues.apache.org/jira/browse/OOZIE-2393
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Muhammad Ehsan ul Haque
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: hcatalog, prepare
> Fix For: 5.0.0
>
> Attachments: OOZIE-2393-00.patch, OOZIE-2393-01.patch
>
>
> The hcat prepare only allows to drop partitions. It would be nice to also 
> allow dropping of table, depending on the URL. The current format of the URL 
> is
> {code}hcat://[metastore server]:[port]/[database name]/[table 
> name]/[partkey1]=[value];[partkey2]=[value]{code}
> where at least one partition must be provided, otherwise the prepare step 
> fails with the fololwing exception.
> {code}
> Starting the execution of prepare actions
> Creating HCatClient for user=ehsan.haq (auth:SIMPLE) and 
> server=thrift://datavault-prod-app2.internal.machines:9083
> Prepare execution in the Launcher Mapper has failed
> Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), Error 
> trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> org.apache.oozie.action.hadoop.LauncherException: Error trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:178)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:450)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: org.apache.oozie.action.hadoop.LauncherException: Error trying to 
> drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:64)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.execute(PrepareActionsDriver.java:89)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.doOperations(PrepareActionsDriver.java:67)
> at 
> org.apache.oozie.action.hadoop.LauncherMapper.executePrepare(LauncherMapper.java:446)
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:174)
> ... 8 more
> Caused by: java.net.URISyntaxException: URI path is not in expected format: 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.util.HCatURI.parse(HCatURI.java:66)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:52)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:48)
> at 
> org.

[jira] [Commented] (OOZIE-2393) Allow table drop in hcat prepare

2016-10-06 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2393:
---

[~abhishekbafna], thank you for adding documentation and even more test cases!
+1 non-binding 

> Allow table drop in hcat prepare
> 
>
> Key: OOZIE-2393
> URL: https://issues.apache.org/jira/browse/OOZIE-2393
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 4.1.0, 4.2.0
>Reporter: Muhammad Ehsan ul Haque
>Assignee: Abhishek Bafna
>Priority: Minor
>  Labels: hcatalog, prepare
> Fix For: 5.0.0
>
> Attachments: OOZIE-2393-00.patch, OOZIE-2393-01.patch
>
>
> The hcat prepare only allows to drop partitions. It would be nice to also 
> allow dropping of table, depending on the URL. The current format of the URL 
> is
> {code}hcat://[metastore server]:[port]/[database name]/[table 
> name]/[partkey1]=[value];[partkey2]=[value]{code}
> where at least one partition must be provided, otherwise the prepare step 
> fails with the fololwing exception.
> {code}
> Starting the execution of prepare actions
> Creating HCatClient for user=ehsan.haq (auth:SIMPLE) and 
> server=thrift://datavault-prod-app2.internal.machines:9083
> Prepare execution in the Launcher Mapper has failed
> Failing Oozie Launcher, Main class 
> [org.apache.oozie.action.hadoop.SqoopMain], exception invoking main(), Error 
> trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> org.apache.oozie.action.hadoop.LauncherException: Error trying to drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:178)
> at org.apache.hadoop.mapred.MapRunner.run(MapRunner.java:54)
> at org.apache.hadoop.mapred.MapTask.runOldMapper(MapTask.java:450)
> at org.apache.hadoop.mapred.MapTask.run(MapTask.java:343)
> at org.apache.hadoop.mapred.YarnChild$2.run(YarnChild.java:163)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:415)
> at 
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1628)
> at org.apache.hadoop.mapred.YarnChild.main(YarnChild.java:158)
> Caused by: org.apache.oozie.action.hadoop.LauncherException: Error trying to 
> drop 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:64)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.execute(PrepareActionsDriver.java:89)
> at 
> org.apache.oozie.action.hadoop.PrepareActionsDriver.doOperations(PrepareActionsDriver.java:67)
> at 
> org.apache.oozie.action.hadoop.LauncherMapper.executePrepare(LauncherMapper.java:446)
> at org.apache.oozie.action.hadoop.LauncherMapper.map(LauncherMapper.java:174)
> ... 8 more
> Caused by: java.net.URISyntaxException: URI path is not in expected format: 
> hcat://datavault-prod-app2.internal.machines:9083/test_rdbms_import_2015110600/test
> at org.apache.oozie.util.HCatURI.parse(HCatURI.java:66)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:52)
> at org.apache.oozie.util.HCatURI.(HCatURI.java:48)
> at 
> org.apache.oozie.action.hadoop.HCatLauncherURIHandler.delete(HCatLauncherURIHandler.java:52)
> ... 12 more
> Oozie Launcher failed, finishing Hadoop job gracefully
> {code}
> h3. Suggestion
> In the URL if the partition is not provided then it should delete the entire 
> table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1986) Add FindBugs report to pre-commit build

2016-10-06 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-1986:
-

In the meanwhile the developer has kindly [*Apache 
2.0d*|https://github.com/adjohnson916/findbugs-diff/blob/master/LICENSE] the 
project, so no worries whatsoever.

> Add FindBugs report to pre-commit build
> ---
>
> Key: OOZIE-1986
> URL: https://issues.apache.org/jira/browse/OOZIE-1986
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Robert Kanter
>Assignee: Andras Piros
> Fix For: 5.0.0
>
> Attachments: OOZIE-1986.001.patch, OOZIE-1986.002.patch, 
> OOZIE-1986.003.patch
>
>
> Now that we have OOZIE-1793, it will be really useful to have the pre-commit 
> build generate a findbugs report.  It should probably before and after the 
> patch and only complain it there are more after.  And it should link to the 
> report.  Ideally, this would do some kind of diff (like Hadoop does) so it's 
> easy to identify the new findbugs items.
> You can generate the findbugs reports by running:
> {noformat}
> mvn verify -DskipTests
> {noformat}
> This also runs checkstyle



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (OOZIE-1814) Oozie should mask any passwords in logs and REST interfaces

2016-10-06 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-1814:
--

+1

> Oozie should mask any passwords in logs and REST interfaces
> ---
>
> Key: OOZIE-1814
> URL: https://issues.apache.org/jira/browse/OOZIE-1814
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Bowen Zhang
>Assignee: Andras Piros
>  Labels: newbie
> Fix For: 4.3.0
>
> Attachments: OOZIE-1814.002.patch, OOZIE-1814.003.patch, 
> OOZIE-1814.004.patch, OOZIE-1814.005.patch, OOZIE-1814.006.patch, 
> OOZIE-1814.007.patch, oozie-1814.patch
>
>
> Following passwords are currently visible in the instrumentation log, REST 
> endpoints, WebUI, and CLI (WebUI and CLI simply call the REST endpoints):
> * {{javax.net.ssl.trustStorePassword}}
> * {{oozie.https.keystore.pass}}
> * {{HADOOP_CREDSTORE_PASSWORD}}
> * {{OOZIE_HTTPS_KEYSTORE_PASSWORD}}
> * {{OOZIE_HTTPS_TRUSTSTORE_PASSWORD}}
> There are a few examples that illustrate password leakage.
> {noformat}
> # grep -i pass /var/log/oozie/oozie-instrumentation.log
> OOZIE_HTTPS_TRUSTSTORE_PASSWORD = password
> javax.net.ssl.trustStorePassword = password
> oozie.https.keystore.pass = password
> HADOOP_CREDSTORE_PASSWORD = password
> OOZIE_HTTPS_KEYSTORE_PASSWORD = password
> CATALINA_OPTS = -Xms603979776 -Xmx603979776 
> -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/tmp/OOZIE-1_OOZIE-1-OOZIE_SERVER-2e75cc1293d9058eef7250a18f347c43_pid30867.hprof
>  -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh 
> -Doozie.home.dir=/usr/lib/oozie 
> -Doozie.config.dir=/var/run/cloudera-scm-agent/process/320-oozie-OOZIE_SERVER 
> -Doozie.log.dir=/var/log/oozie 
> -Doozie.log.file=oozie-cmf-OOZIE-1-OOZIE_SERVER-nightly-1.gce.cloudera.com.log.out
>  -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=log4j.properties 
> -Doozie.log4j.reload=10 -Doozie.http.hostname=nightly-1.gce.cloudera.com 
> -Doozie.http.port=11000 -Djava.net.preferIPv4Stack=true 
> -Doozie.admin.port=11001 -Dderby.stream.error.file=/var/log/oozie/derby.log 
> -Doozie.instance.id=nightly-1.gce.cloudera.com 
> -Djava.library.path=/usr/lib/hadoop/lib/native -Doozie.https.port=11443 
> -Djavax.net.ssl.trustStore=/etc/cdep-ssl-conf/CA_STANDARD/truststore.jks 
> -Djavax.net.ssl.trustStorePassword=password
> {noformat}
> Oozie dumps the env vars and Java sys props to the instrumentation log on 
> startup.
> {noformat}
> # curl --negotiate -u foo:bar -k 
> https://nightly-1.gce.cloudera.com:11443/oozie/v2/admin/os-env | python -m 
> json.tool | grep -i pass
> "CATALINA_OPTS": "-Xms603979776 -Xmx603979776 -XX:+HeapDumpOnOutOfMemoryError 
> -XX:HeapDumpPath=/tmp/OOZIE-1_OOZIE-1-OOZIE_SERVER-2e75cc1293d9058eef7250a18f347c43_pid30867.hprof
>  -XX:OnOutOfMemoryError=/usr/lib64/cmf/service/common/killparent.sh 
> -Doozie.home.dir=/usr/lib/oozie 
> -Doozie.config.dir=/var/run/cloudera-scm-agent/process/320-oozie-OOZIE_SERVER 
> -Doozie.log.dir=/var/log/oozie 
> -Doozie.log.file=oozie-cmf-OOZIE-1-OOZIE_SERVER-nightly-1.gce.cloudera.com.log.out
>  -Doozie.config.file=oozie-site.xml -Doozie.log4j.file=log4j.properties 
> -Doozie.log4j.reload=10 -Doozie.http.hostname=nightly-1.gce.cloudera.com 
> -Doozie.http.port=11000 -Djava.net.preferIPv4Stack=true 
> -Doozie.admin.port=11001 -Dderby.stream.error.file=/var/log/oozie/derby.log 
> -Doozie.instance.id=nightly-1.gce.cloudera.com 
> -Djava.library.path=/usr/lib/hadoop/lib/native -Doozie.https.port=11443 
> -Djavax.net.ssl.trustStore=/etc/cdep-ssl-conf/CA_STANDARD/truststore.jks 
> -Djavax.net.ssl.trustStorePassword=password ",
> "HADOOP_CREDSTORE_PASSWORD": "password",
> "OOZIE_HTTPS_KEYSTORE_PASSWORD": "password",
> "OOZIE_HTTPS_TRUSTSTORE_PASSWORD": "password",
> {noformat}
> {noformat}
> # curl --negotiate -u foo:bar -k 
> https://nightly-1.gce.cloudera.com:11443/oozie/v2/admin/java-sys-properties | 
> python -m json.tool | grep -i pass
> "javax.net.ssl.trustStorePassword": "password",
> "oozie.https.keystore.pass": "password",
> {noformat}
> The REST API has two endpoints, {{admin/os-env}} and 
> {{admin/java-sys-properties}}, which are also available in the Web UI and 
> CLI.  These expose the env vars and Java sys props too.
> We should mask these like we do for the configuration endpoint.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

2016-10-06 Thread Attila Sasvari


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52399/
---

(Updated Oct. 6, 2016, 10:09 p.m.)


Review request for oozie, András Piros, Peter Cseh, Peter Bacsko, and Robert 
Kanter.


Changes
---

Main changes 
* Use ConfigurationService to get SSL settings
- add properties oozie-default.xml
- adjust tests and oozie script
* Refactor: rename some properties
* Run TestEmbeddedOozieServer MockitoJUnitRunner.class)
* Fix version of jetty-plus maven dependency


Repository: oozie-git


Description
---

Embedding jetty into Oozie so that it can run as a standalone application. The 
changes also try to address OOZIE-2317 (i.e. Tomcat 6 is EOL).

New functionality
- New module (server) is added that sets up an embedded Jetty server and start 
Oozie services. Servlet mapping is done by reading web.xml of webapp at 
runtime. JSP is handled with custom code. Server version is not revealed in 
server repsonses.
- SSL protocols and ciphers can be configured via system properties and 
environment variables. Precedence: system properties, environment variables, 
default values
   
Changes in existing code
- Excluded jetty 6 dependencies from core and updated tests accordingly  

Packaging
- oozie.sh is modified so that it starts Oozie with embedded jetty by default. 
If someone would like to use tomcat for any reason, they can set an environment 
variable (e.g. OOZIE_USE_TOMCAT=1).

TODO:
- Add more tests
- Add more documentation
- Code cleanup + refactoring in packaging and core parts
- Maven clean up
- Allow to tune more Jetty settings (for example threadpool)
- More security measures (e.g. protect against clickjacking, CSRF, etc.)
- Update Oozie Documentation


Diffs (updated)
-

  core/src/main/java/org/apache/oozie/util/Instrumentation.java 
fa1e92a0f1fadfb66c5e66fea5f26f57579080e7 
  core/src/main/resources/oozie-default.xml 
e71ebe3b7a85e6b23176ef30713af63847144498 
  distro/pom.xml c50572c57a376b28963d4e7da8ac7df777fe0480 
  distro/src/main/bin/oozie-jetty-server.sh PRE-CREATION 
  distro/src/main/bin/oozie-setup.sh 79b049bccceb2690f8a673a885a615c8d4d9578c 
  distro/src/main/bin/oozie-sys.sh 97d55a2b69c34ede007d4f65cdfc66f1ac2cfd13 
  distro/src/main/bin/oozied.sh a869c3da177c863a068f2af45c7bca9d5cb771ac 
  pom.xml 704a29f4e4805e3e08c2a547b2a375f6b1b2 
  server/pom.xml PRE-CREATION 
  server/src/main/assemblies/empty.xml PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java 
PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/JspHandler.java PRE-CREATION 
  server/src/main/java/org/apache/oozie/server/SSLServerConnectorFactory.java 
PRE-CREATION 
  server/src/main/resources/checkstyle-header.txt PRE-CREATION 
  server/src/main/resources/checkstyle.xml PRE-CREATION 
  server/src/test/java/org/apache/oozie/server/TestEmbeddedOozieServer.java 
PRE-CREATION 
  
server/src/test/java/org/apache/oozie/server/TestSSLServerConnectorFactory.java 
PRE-CREATION 
  src/main/assemblies/distro.xml 1ffbfd6d2ba33b390999e9094cbb336fbce45c21 

Diff: https://reviews.apache.org/r/52399/diff/


Testing
---

- Tested basic functionality by executing a workflow that uses the sample 
JavaAction
- without SSL - on a 2.4.0 pseudo Hadoop cluster
- SSL with Kerberos is using a test CDH cluster 
- Added new unit tests that check
- If oozie.ssl.enabled is not specified, server starts without SSL settings 
- If oozie.ssl.enabled is specified, server starts with SSL settings
- SSL protocols and ciphers can be configured via system properties and 
environment variables 
- Ran subset of tests using Hadoop-2 profile
- mvn clean package assembly:single   -DjavaVersion=1.8 -DtargetVersion=1.7 
 -Dtest=TestJavaActionExecutor  -Phadoop-2 -Dhadoop.version=2.4.0


Thanks,

Attila Sasvari

[jira] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-06 Thread Attila Sasvari (JIRA)


 [ 
https://issues.apache.org/jira/browse/OOZIE-2666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Attila Sasvari updated OOZIE-2666:
--
Attachment: OOZIE-2666.PATCH-05.patch

> Support embedding Jetty into Oozie
> --
>
> Key: OOZIE-2666
> URL: https://issues.apache.org/jira/browse/OOZIE-2666
> Project: Oozie
>  Issue Type: Sub-task
>  Components: core
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2666.PATCH-01.patch, OOZIE-2666.PATCH-02.patch, 
> OOZIE-2666.PATCH-03.patch, OOZIE-2666.PATCH-05.patch
>
>
> The purpose of this task is to allow Oozie to run as a standalone application 
> rather than being deployed to a container inside a WAR file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2645) Drop Instrumentation in favor of Metrics

2016-10-06 Thread Robert Kanter (JIRA)


 [ 
https://issues.apache.org/jira/browse/OOZIE-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-2645:
-
Fix Version/s: 5.0.0

> Drop Instrumentation in favor of Metrics
> 
>
> Key: OOZIE-2645
> URL: https://issues.apache.org/jira/browse/OOZIE-2645
> Project: Oozie
>  Issue Type: Improvement
>  Components: monitoring
>Affects Versions: trunk
>Reporter: Robert Kanter
> Fix For: 5.0.0
>
>
> OOZIE-1817 added the option to use DropWizard Metrics instead of our 
> homegrown Instrumentation.  We left the Instrumentation as the default for 
> compatibility; in Oozie 5, we should drop Instrumentation and only have 
> Metrics.
> We can also use this opportunity to clean up the code and interface for 
> Metrics, which currently has to conform to Instrumentation for pluggability.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (OOZIE-2645) Drop Instrumentation in favor of Metrics

2016-10-06 Thread Robert Kanter (JIRA)


 [ 
https://issues.apache.org/jira/browse/OOZIE-2645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Kanter updated OOZIE-2645:
-
Priority: Blocker  (was: Major)

> Drop Instrumentation in favor of Metrics
> 
>
> Key: OOZIE-2645
> URL: https://issues.apache.org/jira/browse/OOZIE-2645
> Project: Oozie
>  Issue Type: Improvement
>  Components: monitoring
>Affects Versions: trunk
>Reporter: Robert Kanter
>Priority: Blocker
> Fix For: 5.0.0
>
>
> OOZIE-1817 added the option to use DropWizard Metrics instead of our 
> homegrown Instrumentation.  We left the Instrumentation as the default for 
> compatibility; in Oozie 5, we should drop Instrumentation and only have 
> Metrics.
> We can also use this opportunity to clean up the code and interface for 
> Metrics, which currently has to conform to Instrumentation for pluggability.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

2016-10-06 Thread Robert Kanter

---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52399/#review151728
---

core/src/main/java/org/apache/oozie/util/Instrumentation.java (line 783)

Why is this change needed?

core/src/main/resources/oozie-default.xml (line 2514)

I think we should make these property names consistent.  Some start with 
oozie.ssl and some start with oozie.https but they're all related.

I'd vote for oozie.https given that (a) we're using http(s) for everything 
and (b) ssl is technically outdated in favor of tls, though they're often used 
interchangebly; with oozie.https we don't have to think about that :)

distro/pom.xml (lines 116 - 128)

What is this for?

distro/src/main/bin/oozie-jetty-server.sh (line 1)

Please run all new/updated shell scripts through shellcheck 
(https://www.shellcheck.net/).  It finds various problems and best practice 
violations (kind of like findbugs).  You can even install it on your Mac with 
Homebrew or MacPorts.

distro/src/main/bin/oozie-jetty-server.sh (lines 40 - 61)

IMO, we should move as many of these as possible to oozie-default/site.  We 
had a bunch of these as JVM properties before because of Tomcat and other 
reasons, but it would be good to have them all in the same place as other 
config properties.  At the very least, the https/ssl ones (the other ones are 
probably out of scope for this JIRA).

distro/src/main/bin/oozie-jetty-server.sh (line 187)

Can we set this up in such that there is no war file when using Jetty?

server/pom.xml (line 26)

Leave off the  in this pom, and instead define them all in the 
root pom.

server/src/main/assemblies/empty.xml (lines 9 - 11)

Whitespace

server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java (lines 46 
- 47)

Should these be configurable?  IIRC, we had to increase one of these in 
Tomcat at one point for some reason.

server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java (line 84)

We now typically get the Configuration by doing 
ConfigurationService.get("property-name")

server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java (line 136)

It would be good to do a services.destroy() when shutting down because many 
Services have some sort of cleanup or disconnect that they do.

server/src/main/java/org/apache/oozie/server/JspHandler.java (line 51)

This typically points to /tmp right?  In a long running Oozie Server, might 
we run into problem where the OS cleans this up?

- Robert Kanter

On Oct. 6, 2016, 10:09 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52399/
> ---
> 
> (Updated Oct. 6, 2016, 10:09 p.m.)
> 
> 
> Review request for oozie, András Piros, Peter Cseh, Peter Bacsko, and Robert 
> Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Embedding jetty into Oozie so that it can run as a standalone application. 
> The changes also try to address OOZIE-2317 (i.e. Tomcat 6 is EOL).
> 
> New functionality
> - New module (server) is added that sets up an embedded Jetty server and 
> start Oozie services. Servlet mapping is done by reading web.xml of webapp at 
> runtime. JSP is handled with custom code. Server version is not revealed in 
> server repsonses.
> - SSL protocols and ciphers can be configured via system properties and 
> environment variables. Precedence: system properties, environment variables, 
> default values
>
> Changes in existing code
> - Excluded jetty 6 dependencies from core and updated tests accordingly  
> 
> Packaging
> - oozie.sh is modified so that it starts Oozie with embedded jetty by 
> default. If someone would like to use tomcat for any reason, they can set an 
> environment variable (e.g. OOZIE_USE_TOMCAT=1).
> 
> TODO:
> - Add more tests
> - Add more documentation
> - Code cleanup + refactoring in packaging and core parts
> - Maven clean up
> - Allow to tune more Jetty settings (for example threadpool)
> - More security measures (e.g. protect against clickjacking, CSRF, etc.)
> - Upda

[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie

2016-10-06 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2666:
--

Testing JIRA OOZIE-2666

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:red}-1{color} the patch contains 12 line(s) with tabs
.{color:red}-1{color} the patch contains 2 line(s) with trailing spaces
.{color:red}-1{color} the patch contains 9 line(s) longer than 132 
characters
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:red}-1 RAT{color}
.{color:red}-1{color} the patch seems to introduce 3 new RAT warning(s)
{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:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:red}-1{color} the patch seems to introduce 3 new javac warning(s)
{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: 1821
{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/3360/

> Support embedding Jetty into Oozie
> --
>
> Key: OOZIE-2666
> URL: https://issues.apache.org/jira/browse/OOZIE-2666
> Project: Oozie
>  Issue Type: Sub-task
>  Components: core
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2666.PATCH-01.patch, OOZIE-2666.PATCH-02.patch, 
> OOZIE-2666.PATCH-03.patch, OOZIE-2666.PATCH-05.patch
>
>
> The purpose of this task is to allow Oozie to run as a standalone application 
> rather than being deployed to a container inside a WAR file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Build failed in Jenkins: oozie-trunk-precommit-build #3360

2016-10-06 Thread Apache Jenkins Server

See 

Changes:

[rkanter] OOZIE-1814 Oozie should mask any passwords in logs and REST interfaces

--
[...truncated 5823 lines...]
[INFO] Copying jdo-api-3.0.1.jar to 

[INFO] Copying hive-shims-0.20S-0.13.1.jar to 

[INFO] Copying oozie-hadoop-utils-hadoop-2-4.4.0-SNAPSHOT.jar to 

[INFO] Copying log4j-1.2.17.jar to 

[INFO] Copying tools.jar to 

[INFO] Copying netty-3.6.2.Final.jar to 

[INFO] Copying apache-log4j-extras-1.2.17.jar to 

[INFO] Copying commons-digester-1.8.jar to 

[INFO] Copying activation-1.1.jar to 

[INFO] Copying collections-generic-4.01.jar to 

[INFO] Copying hive-shims-0.23-0.13.1.jar to 

[INFO] Copying xmlenc-0.52.jar to 

[INFO] Copying httpcore-4.3.3.jar to 

[INFO] Copying openjpa-persistence-2.4.1.jar to 

[INFO] Copying jetty-io-9.2.19.v20160908.jar to 

[INFO] Copying hive-shims-0.20-0.13.1.jar to 

[INFO] Copying jetty-http-9.2.19.v20160908.jar to 

[INFO] Copying jetty-plus-9.2.19.v20160908.jar to 

[INFO] Copying hive-serde-0.13.1.jar to 

[INFO] Copying antlr-2.7.7.jar to 

[INFO] Copying jackson-databind-2.2.2.jar to 

[INFO] Copying oozie-sharelib-oozie-4.4.0-SNAPSHOT.jar to 

[INFO] Copying commons-beanutils-core-1.8.0.jar to 

[INFO] Copying hadoop-yarn-server-common-2.4.0.jar to 

[INFO] Copying geronimo-j2ee-management_1.1_spec-1.0.1.jar to 

[INFO] Copying datanucleus-core-3.2.10.jar to 

[INFO] Copying slf4j-log4j12-1.6.6.jar to 

[INFO] Copying aopalliance-1.0.jar to 

[INFO] Copying hadoop-mapreduce-client-core-2.4.0.jar to 

[INFO] Copying datanucleus-api-jdo-3.2.6.jar to

Re: Review Request 52217: OOZIE-2591 OYA: Java Action

2016-10-06 Thread Robert Kanter


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52217/#review151745
---




core/src/main/java/org/apache/oozie/service/Services.java (line 308)


if you put the rex as the last argument in the log.fatal, it should print 
out the stack trace to the log.  printStateTrace will go to stderr.



core/src/test/java/org/apache/oozie/action/hadoop/TestLauncher.java (line 45)


Weren't we going to change the min Hadoop version to 2.6.0?



core/src/test/java/org/apache/oozie/test/XTestCase.java (line 1225)


Yes.  Otherwise, the waitFor could timeout and you wouldn't know.

In general, you need to check the same condition in a waitFor and right 
after it to handle the timeout case.



core/src/test/java/org/apache/oozie/test/XTestCase.java (line 1237)


You don't need to bother with the MutableObject here.  That was only needed 
in the other method because there was an annonymous inner class.



sharelib/oozie/src/main/java/org/apache/oozie/action/hadoop/LauncherAM.java 
(line 415)


Looks that way.  SequenceWriter.createWriter must take care of this.


- Robert Kanter


On Sept. 26, 2016, 12:28 p.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52217/
> ---
> 
> (Updated Sept. 26, 2016, 12:28 p.m.)
> 
> 
> Review request for oozie, Jaydeep Vishwakarma, Purshotam Shah, Robert Kanter, 
> and Rohini Palaniswamy.
> 
> 
> Bugs: OOZIE-2591
> https://issues.apache.org/jira/browse/OOZIE-2591
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Java action is working.
> There are some things in there which are still temporary, we're opening 
> follow-up jiras to address them.
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/WorkflowJobBean.java 
> 55d79a5d5e5e4efab9eb832e9341a16bcf8959cc 
>   core/src/main/java/org/apache/oozie/action/hadoop/Credentials.java 
> eadb47b07d157f45f086517ab41c4b9826f003f0 
>   core/src/main/java/org/apache/oozie/action/hadoop/CredentialsProvider.java 
> 6fe22fbd2fca5d873d58ece60f20d0f131371475 
>   core/src/main/java/org/apache/oozie/action/hadoop/DistcpActionExecutor.java 
> 99652e836a012811fb0cbd78856ccf5f0ff56b70 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsActionExecutor.java 
> 121cd49bc1077530892aa593581f50ce89ac365d 
>   core/src/main/java/org/apache/oozie/action/hadoop/FsELFunctions.java 
> 801bfe6eb212b549888f0e9fb7df7b65bcf59393 
>   core/src/main/java/org/apache/oozie/action/hadoop/HCatCredentialHelper.java 
> 428975e4625b32c4c90284a93a726df490f58b70 
>   core/src/main/java/org/apache/oozie/action/hadoop/HadoopELFunctions.java 
> c32288783d8e5cb0f3bf758fa0580a6cd7aed93a 
>   core/src/main/java/org/apache/oozie/action/hadoop/HbaseCredentials.java 
> 307f565786ad77f5a35b5790bd5b052b04c6eac8 
>   core/src/main/java/org/apache/oozie/action/hadoop/Hive2ActionExecutor.java 
> 9ba6318a77ffa17e93c8d5babd5ee97ba96dc57f 
>   core/src/main/java/org/apache/oozie/action/hadoop/HiveActionExecutor.java 
> a8509578684287e0aed9a76dcc9778e3ee9a54e0 
>   core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java 
> d573fc35a2f2d971c97a1ff046469b0698ee92cb 
>   core/src/main/java/org/apache/oozie/action/hadoop/LauncherMapperHelper.java 
> 07d1262d1410f089de40a32367351830c4d7269c 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/MapReduceActionExecutor.java
>  de8290efb78739596e79dea41e1be92c70909333 
>   core/src/main/java/org/apache/oozie/action/hadoop/OozieJobInfo.java 
> 581d3b3219eff882f961c8e495611e873c6a5a52 
>   core/src/main/java/org/apache/oozie/action/hadoop/PigActionExecutor.java 
> 8b2dc16db80ad602911f1f64e60cfad41b198922 
>   
> core/src/main/java/org/apache/oozie/action/hadoop/ScriptLanguageActionExecutor.java
>  f2541265ca71fb7f3b053c59775ef5e23d0d8f94 
>   core/src/main/java/org/apache/oozie/action/hadoop/ShellActionExecutor.java 
> 4fdd3ff9d5d611916e1312f669a4df1f014f7970 
>   core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java 
> 6a41235768bc87542e8c041b78ecace260fc96ba 
>   core/src/main/java/org/apache/oozie/action/hadoop/SqoopActionExecutor.java 
> 82e5f0cedd4c32d6b2d269ffcc080172c787ec49 
>   core/src/main/java/org/apache/oozie/service/JPAService.java 
> fd3f6cb2242619ec7b7fbce68e0675fb1324b6f5 
>   core/src/main/java/org/apache/oozie/service/Services.java 
> 829d5f5cd90c86e6cba9854dc0b4b7df570b8900 
>   core/src/main/java/org/apache/oozie/service/ShareLibService.java 
> fa23

Build failed in Jenkins: oozie-trunk-find-patches-available #135492

2016-10-06 Thread Apache Jenkins Server

See 

--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (yahoo-not-h2 Hadoop Mapreduce Hdfs Pig) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/oozie.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/oozie.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 962d650bdc5522d39d49ba8ee2b3fc1634c625ec 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 962d650bdc5522d39d49ba8ee2b3fc1634c625ec
 > git rev-list 962d650bdc5522d39d49ba8ee2b3fc1634c625ec # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson1908138936019810754.sh
mkdir: cannot create directory 
':
 File exists
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed

  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
100 533690 533690 0  85114  0 --:--:-- --:--:-- --:--:-- 85118
100  403k0  403k0 0   236k  0 --:--:--  0:00:01 --:--:--  236k
100  712k0  712k0 0   266k  0 --:--:--  0:00:02 --:--:--  266k
100 1080k0 1080k0 0   296k  0 --:--:--  0:00:03 --:--:--  296k
100 1202k0 1202k0 0   283k  0 --:--:--  0:00:04 --:--:--  283k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

Jenkins build is back to normal : oozie-trunk-find-patches-available #135493

2016-10-06 Thread Apache Jenkins Server

See

[jira] Subscription: Oozie Patch Available

2016-10-06 Thread jira

Issue Subscription
Filter: Oozie Patch Available (78 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2694  Add logging for FsActionExecutor 
https://issues.apache.org/jira/browse/OOZIE-2694
OOZIE-2693  SimpleHCatDependencyCache.removeMissingDependency can throw NPE
https://issues.apache.org/jira/browse/OOZIE-2693
OOZIE-2692  Oozie job submit doesn't report error message to user if there is 
any issue with job conf
https://issues.apache.org/jira/browse/OOZIE-2692
OOZIE-2691  Show workflow action retry count to UI
https://issues.apache.org/jira/browse/OOZIE-2691
OOZIE-2690  OOZIE NPE while executing kill()
https://issues.apache.org/jira/browse/OOZIE-2690
OOZIE-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2674  Improve oozie commads documentation
https://issues.apache.org/jira/browse/OOZIE-2674
OOZIE-2670  Upgrade Hbase to 1.2
https://issues.apache.org/jira/browse/OOZIE-2670
OOZIE-2668  Status update and recovery problems when coord action and its 
children not in sync
https://issues.apache.org/jira/browse/OOZIE-2668
OOZIE-2666  Support embedding Jetty into Oozie
https://issues.apache.org/jira/browse/OOZIE-2666
OOZIE-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
OOZIE-2658  --driver-class-path can overwrite the classpath in SparkMain
https://issues.apache.org/jira/browse/OOZIE-2658
OOZIE-2654  Zookeeper dependent services should not depend on Connectionstate 
to be valid before cleaning up
https://issues.apache.org/jira/browse/OOZIE-2654
OOZIE-2652  Skip trash while deleting hive table partition
https://issues.apache.org/jira/browse/OOZIE-2652
OOZIE-2650  Retry coord start on database exceptions
https://issues.apache.org/jira/browse/OOZIE-2650
OOZIE-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2630  Oozie Coordinator EL Functions to get first day of the week/month
https://issues.apache.org/jira/browse/OOZIE-2630
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues.apache.org/jira/browse/OOZIE-2618
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues.apache.org/jira/browse/OOZIE-2616
OOZIE-2613  Upgrade hive version from 0.13.1 to 1.2.0
https://issues.apache.org/jira/browse/OOZIE-2613
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues.apache.org/jira/browse/OOZIE-2573
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues.apache.org/jira/browse/OOZIE-2564
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues.apache.org/jira/browse/OOZIE-2534
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues.apache.org/jira/browse/OOZIE-2528
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues.apache.org/jira/browse/OOZIE-2518
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues.apache.org/jira/browse/OOZIE-2513
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues.apache.org/jira/browse/OOZIE-2499
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues.apache.org/jira/browse/OOZIE-2495
OOZIE-2473  Connection pool for SMTP connection
https://issues.apache.org/jira/browse/OOZIE-2473
OOZIE-2461  Workflow, Coordinator and Bundle job querying should have last 
modified filter
https://issues.apache.org/jira/browse/OOZIE-2461
OOZIE-2458  'oozie-setup.sh sharelib create' should ensure uploaded jars are 
world readable
https://issues.apache.org/jira/browse/OOZIE-2458
OOZIE-2457  Oozie log parsing regex consume more than 90% cpu
https://issues.apache.org/jira/browse/OOZIE-2457
OOZIE-2427  With Kerberos enabled, the authentication failure for the 
javascript resources under /ext-2.2 
https://issues.apache.org/jira/browse/OOZIE-2427
O

[jira] Subscription: Oozie Patch Available

2016-10-06 Thread jira

Issue Subscription
Filter: Oozie Patch Available (86 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2619  Make  Hive action defaults to match hive defaults when running from 
command line
https://issues-test.apache.org/jira/browse/OOZIE-2619
OOZIE-2618  Include hive-common in hive-beeline as compile component for 
hive-server2 (hive2 action)
https://issues-test.apache.org/jira/browse/OOZIE-2618
OOZIE-2617  Read properties files in action configurations
https://issues-test.apache.org/jira/browse/OOZIE-2617
OOZIE-2616  Add Tez profile for Hive and Pig sharelibs
https://issues-test.apache.org/jira/browse/OOZIE-2616
OOZIE-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues-test.apache.org/jira/browse/OOZIE-2606
OOZIE-2589  CompletedActionXCommand priority param is of no effect
https://issues-test.apache.org/jira/browse/OOZIE-2589
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues-test.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues-test.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues-test.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues-test.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues-test.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues-test.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues-test.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues-test.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues-test.apache.org/jira/browse/OOZIE-2569
OOZIE-2568  SSH  action pretends to retry automaticly when it failed
https://issues-test.apache.org/jira/browse/OOZIE-2568
OOZIE-2564  Create new log4j config for unit tests so that logged messages 
contain threads
https://issues-test.apache.org/jira/browse/OOZIE-2564
OOZIE-2552  Update ActiveMQ version for security and other fixes
https://issues-test.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues-test.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues-test.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues-test.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues-test.apache.org/jira/browse/OOZIE-2528
OOZIE-2521  Filter options are case sensitive for jobtye=bundle
https://issues-test.apache.org/jira/browse/OOZIE-2521
OOZIE-2518  Oozie is creating many files and directories in /tmp per day
https://issues-test.apache.org/jira/browse/OOZIE-2518
OOZIE-2517  Add support for startCreatedTime and endCreatedTime filters for 
coord and bundles
https://issues-test.apache.org/jira/browse/OOZIE-2517
OOZIE-2513  log.scan.duration should not be used for error and audit logs
https://issues-test.apache.org/jira/browse/OOZIE-2513
OOZIE-2512  ShareLibservice returns incorrect path for jar
https://issues-test.apache.org/jira/browse/OOZIE-2512
OOZIE-2508  Documentation change for Coord action rerun [OOZIE-1735]
https://issues-test.apache.org/jira/browse/OOZIE-2508
OOZIE-2501  ZK reentrant lock doesn't work for few cases
https://issues-test.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues-test.apache.org/jira/browse/OOZIE-2500
OOZIE-2499  map-reduce launcher does not need distributed files, archives 
except  jar of input/outputformat class
https://issues-test.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components 
https://issues-test.apache.org/jira/browse/OOZIE-2498
OOZIE-2495  change action status from  ErrorType.NON_TRANSIENT to TRANSIENT 
when SSH action occurs AUTH_FAILED occasionally
https://issues-test.apache.org/jira/browse/OOZIE-2495
OOZIE-2491  oozie acl cannot specify group,it does`t work
https://issues-test.apache.org/jira/browse/OOZIE-2491
OOZIE

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

2016-10-06 Thread Attila Sasvari



> On Oct. 6, 2016, 11:04 p.m., Robert Kanter wrote:
> > server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java, line 
> > 84
> > 
> >
> > We now typically get the Configuration by doing 
> > ConfigurationService.get("property-name")

Static method calls are not really good for making the code testable. We can 
create a wrapper object that simply calls 
ConfigurationService.get("property-name"), adn mock that in the the test, but I 
believe that is not the proper way to go.


- Attila


---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/52399/#review151728
---


On Oct. 6, 2016, 10:09 p.m., Attila Sasvari wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/52399/
> ---
> 
> (Updated Oct. 6, 2016, 10:09 p.m.)
> 
> 
> Review request for oozie, András Piros, Peter Cseh, Peter Bacsko, and Robert 
> Kanter.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Embedding jetty into Oozie so that it can run as a standalone application. 
> The changes also try to address OOZIE-2317 (i.e. Tomcat 6 is EOL).
> 
> New functionality
> - New module (server) is added that sets up an embedded Jetty server and 
> start Oozie services. Servlet mapping is done by reading web.xml of webapp at 
> runtime. JSP is handled with custom code. Server version is not revealed in 
> server repsonses.
> - SSL protocols and ciphers can be configured via system properties and 
> environment variables. Precedence: system properties, environment variables, 
> default values
>
> Changes in existing code
> - Excluded jetty 6 dependencies from core and updated tests accordingly  
> 
> Packaging
> - oozie.sh is modified so that it starts Oozie with embedded jetty by 
> default. If someone would like to use tomcat for any reason, they can set an 
> environment variable (e.g. OOZIE_USE_TOMCAT=1).
> 
> TODO:
> - Add more tests
> - Add more documentation
> - Code cleanup + refactoring in packaging and core parts
> - Maven clean up
> - Allow to tune more Jetty settings (for example threadpool)
> - More security measures (e.g. protect against clickjacking, CSRF, etc.)
> - Update Oozie Documentation
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/util/Instrumentation.java 
> fa1e92a0f1fadfb66c5e66fea5f26f57579080e7 
>   core/src/main/resources/oozie-default.xml 
> e71ebe3b7a85e6b23176ef30713af63847144498 
>   distro/pom.xml c50572c57a376b28963d4e7da8ac7df777fe0480 
>   distro/src/main/bin/oozie-jetty-server.sh PRE-CREATION 
>   distro/src/main/bin/oozie-setup.sh 79b049bccceb2690f8a673a885a615c8d4d9578c 
>   distro/src/main/bin/oozie-sys.sh 97d55a2b69c34ede007d4f65cdfc66f1ac2cfd13 
>   distro/src/main/bin/oozied.sh a869c3da177c863a068f2af45c7bca9d5cb771ac 
>   pom.xml 704a29f4e4805e3e08c2a547b2a375f6b1b2 
>   server/pom.xml PRE-CREATION 
>   server/src/main/assemblies/empty.xml PRE-CREATION 
>   server/src/main/java/org/apache/oozie/server/EmbeddedOozieServer.java 
> PRE-CREATION 
>   server/src/main/java/org/apache/oozie/server/JspHandler.java PRE-CREATION 
>   server/src/main/java/org/apache/oozie/server/SSLServerConnectorFactory.java 
> PRE-CREATION 
>   server/src/main/resources/checkstyle-header.txt PRE-CREATION 
>   server/src/main/resources/checkstyle.xml PRE-CREATION 
>   server/src/test/java/org/apache/oozie/server/TestEmbeddedOozieServer.java 
> PRE-CREATION 
>   
> server/src/test/java/org/apache/oozie/server/TestSSLServerConnectorFactory.java
>  PRE-CREATION 
>   src/main/assemblies/distro.xml 1ffbfd6d2ba33b390999e9094cbb336fbce45c21 
> 
> Diff: https://reviews.apache.org/r/52399/diff/
> 
> 
> Testing
> ---
> 
> - Tested basic functionality by executing a workflow that uses the sample 
> JavaAction
> - without SSL - on a 2.4.0 pseudo Hadoop cluster
> - SSL with Kerberos is using a test CDH cluster 
> - Added new unit tests that check
> - If oozie.ssl.enabled is not specified, server starts without SSL 
> settings 
> - If oozie.ssl.enabled is specified, server starts with SSL settings
> - SSL protocols and ciphers can be configured via system properties and 
> environment variables 
> - Ran subset of tests using Hadoop-2 profile
> - mvn clean package assembly:single   -DjavaVersion=1.8 
> -DtargetVersion=1.7  -Dtest=TestJavaActionExecutor  -Phadoop-2 
> -Dhadoop.version=2.4.0
> 
> 
> Thanks,
> 
> Attila Sasvari
> 
>

[jira] [Commented] (OOZIE-2613) Upgrade hive version from 0.13.1 to 1.2.0

[jira] [Commented] (OOZIE-1814) Oozie should mask any passwords in logs and REST interfaces

[jira] [Updated] (OOZIE-2393) Allow table drop in hcat prepare

Re: Review Request 52519: Allow table drop in hcat prepare

Build failed in Jenkins: oozie-trunk-find-patches-available #135445

Jenkins build is back to normal : oozie-trunk-find-patches-available #135446

Jenkins build is back to normal : oozie-trunk-precommit-build #3359

[jira] [Commented] (OOZIE-2393) Allow table drop in hcat prepare

[jira] [Commented] (OOZIE-2393) Allow table drop in hcat prepare

[jira] [Commented] (OOZIE-1986) Add FindBugs report to pre-commit build

[jira] [Commented] (OOZIE-1814) Oozie should mask any passwords in logs and REST interfaces

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

[jira] [Updated] (OOZIE-2666) Support embedding Jetty into Oozie

[jira] [Updated] (OOZIE-2645) Drop Instrumentation in favor of Metrics

[jira] [Updated] (OOZIE-2645) Drop Instrumentation in favor of Metrics

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

[jira] [Commented] (OOZIE-2666) Support embedding Jetty into Oozie

Build failed in Jenkins: oozie-trunk-precommit-build #3360

Re: Review Request 52217: OOZIE-2591 OYA: Java Action

Build failed in Jenkins: oozie-trunk-find-patches-available #135492

Jenkins build is back to normal : oozie-trunk-find-patches-available #135493

[jira] Subscription: Oozie Patch Available

[jira] Subscription: Oozie Patch Available

Re: Review Request 52399: OOZIE-2666 Support embedding Jetty into Oozie

24 matches

Site Navigation

Mail list logo

Footer information