[jira] Subscription: Oozie Patch Available

[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

[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (92 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2817  Increase test case stability in pre-commit job
https://issues.apache.org/jira/browse/OOZIE-2817
OOZIE-2816  Strip out the first command word from Sqoop action if its "sqoop"
https://issues.apache.org/jira/browse/OOZIE-2816
OOZIE-2813  Remove tabs and trailing whitespaces from oozie-defaul.xml
https://issues.apache.org/jira/browse/OOZIE-2813
OOZIE-2807  Oozie gets RM delegation token even for checking job status
https://issues.apache.org/jira/browse/OOZIE-2807
OOZIE-2796  oozie.action.keep.action.dir not getting noticed
https://issues.apache.org/jira/browse/OOZIE-2796
OOZIE-2795  Create lib directory or symlink for Oozie CLI during packaging
https://issues.apache.org/jira/browse/OOZIE-2795
OOZIE-2791  ShareLib installation may fail on busy Hadoop clusters
https://issues.apache.org/jira/browse/OOZIE-2791
OOZIE-2785  Master is not compiling with hadoop-1 profile
https://issues.apache.org/jira/browse/OOZIE-2785
OOZIE-2784  Include WEEK as a parameter in the Coordinator Expression Language 
Evaulator
https://issues.apache.org/jira/browse/OOZIE-2784
OOZIE-2780  Upgrade hadoop-common version to 2.6.0
https://issues.apache.org/jira/browse/OOZIE-2780
OOZIE-2779  Mask Hive2 action Beeline JDBC password
https://issues.apache.org/jira/browse/OOZIE-2779
OOZIE-2769  Extend FS action to allow setrep on a file
https://issues.apache.org/jira/browse/OOZIE-2769
OOZIE-2753  Update Docs for Jetty Tomcat changes
https://issues.apache.org/jira/browse/OOZIE-2753
OOZIE-2751  LocalOozieClient is missing methods from OozieClient
https://issues.apache.org/jira/browse/OOZIE-2751
OOZIE-2746  Several tests failure in TestV2ValidateServlet.java
https://issues.apache.org/jira/browse/OOZIE-2746
OOZIE-2739  Remove property expansion pattern from ShellMain's log4j properties 
content
https://issues.apache.org/jira/browse/OOZIE-2739
OOZIE-2736  Reduce the number of threads during test execution
https://issues.apache.org/jira/browse/OOZIE-2736
OOZIE-2733  change org.apache.hadoop.fs.permission.AccessControlException to 
org.apache.hadoop.security.AccessControlException
https://issues.apache.org/jira/browse/OOZIE-2733
OOZIE-2726  Flaky test due to daylight saving changes
https://issues.apache.org/jira/browse/OOZIE-2726
OOZIE-2718  Improve -dryrun for bundles
https://issues.apache.org/jira/browse/OOZIE-2718
OOZIE-2713  Provide an option to log out contents of the localized jar files
https://issues.apache.org/jira/browse/OOZIE-2713
OOZIE-2701  Oozie to support Multiple HCatalog URIs
https://issues.apache.org/jira/browse/OOZIE-2701
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-2684  Bad database schema error for WF_ACTIONS table
https://issues.apache.org/jira/browse/OOZIE-2684
OOZIE-2681  fix javadoc to compile on JDK8 again
https://issues.apache.org/jira/browse/OOZIE-2681
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-2662  DB migration fails if DB is too big
https://issues.apache.org/jira/browse/OOZIE-2662
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-2644  Skip queuing Notification Commands when there's nothing to notify
https://issues.apache.org/jira/browse/OOZIE-2644
OOZIE-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2629  Get OozieShareLibCLI to perform a final rename to destPath when 
creating a Sharelib
https://issues.apache.org/jira/browse/OOZIE-2629
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-2608  Comma in oozie.service.JPAService.jdbc.password value results in 
authentication error
https://issues.apache.org/jira/browse/OOZIE-2608
OOZIE-2585  Disable or remove test case 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) 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 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 c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c8748d221f8265c16e37383e8b3f1572bb613083
 > git rev-list c8748d221f8265c16e37383e8b3f1572bb613083 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson6507720550489951751.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  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0  0 0 
   0 00 0  0  0 --:--:--  0:00:04 --:--:-- 0  0 0   
 0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0  0 0
0 00 0  0  0 --:--:--  0:00:06 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:07 --:--:-- 0  0 00   
  00 0  0  0 --:--:--  0:00:08 --:--:-- 0  0 00 
00 0  0  0 --:--:--  0:00:09 --:--:-- 0  0 00 0 
   0 0  0  0 --:--:--  0:00:10 --:--:-- 0  0 00 0   
 0 0  0  0 --:--:--  0:00:11 --:--:-- 0  0 00 0
0 0  0  0 --:--:--  0:00:12 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:13 --:--:-- 0  0 00 00   
  0  0  0 --:--:--  0:00:14 --:--:-- 0  0 00 00 
0  0  0 --:--:--  0:00:15 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:16 --:--:-- 0  0 00 00 0   
   0  0 --:--:--  0:00:17 --:--:-- 0  0 00 00 0 
 0  0 --:--:--  0:00:18 --:--:-- 0  0 00 00 0  
0  0 --:--:--  0:00:19 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:20 --:--:-- 0  0 00 00 0  0   
   0 --:--:--  0:00:21 --:--:-- 0  0 00 00 0  0 
 0 --:--:--  0:00:22 --:--:-- 0  0 00 00 0  0  
0 --:--:--  0:00:23 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:24 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:25 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:26 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:27 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:28 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:29 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:30 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:31 --:--:-- 0  0 00 00 0  0  0 
--:--:--  0:00:31 --:--:-- 0
Warning: Transient problem: HTTP error Will retry in 1 seconds. 3 retries 
Warning: left.
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0  
0 00 00 0  0  0 --:--:--  0:00:01 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:02 --:--:-- 0  0   
  00 00 0  0  0 --:--:--  0:00:03 --:--:-- 0  0 
00 00 0  0  0 --:--:--  0:00:04 --:--:-- 0  0 0 
   0 00 0  0  0 --:--:--  0:00:05 --:--:-- 0  0 0   
 0 00 0  0  0 --:--:--  0:00:06 --:--:-- 0  0 0
0 00 0  0  0 --:--:--  0:00:07 --:--:-- 0  0 00 
00 0  0  0 

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 


--
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) 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 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 c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f c8748d221f8265c16e37383e8b3f1572bb613083
 > git rev-list c8748d221f8265c16e37383e8b3f1572bb613083 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson5274243980199586532.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 --:--:-- --:--:-- --:--:-- 
0curl: (7) Failed to connect to issues.apache.org port 443: Connection refused
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

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

[Apache Jenkins Server]

See 


--
Started by remote host 127.0.0.1
[EnvInject] - Loading node environment variables.
Building remotely on H10 (Hadoop) 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 fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/oozie.git 
 > +refs/heads/*:refs/remotes/origin/*
ERROR: Error fetching remote repo 'origin'
hudson.plugins.git.GitException: Failed to fetch from 
https://git-wip-us.apache.org/repos/asf/oozie.git
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:806)
at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1066)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1097)
at hudson.scm.SCM.checkout(SCM.java:495)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1278)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:604)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:529)
at hudson.model.Run.execute(Run.java:1728)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:404)
Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
--progress https://git-wip-us.apache.org/repos/asf/oozie.git 
+refs/heads/*:refs/remotes/origin/*" returned status code 128:
stdout: 
stderr: fatal: unable to access 
'https://git-wip-us.apache.org/repos/asf/oozie.git/': gnutls_handshake() 
failed: A TLS packet with unexpected length was received.

at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1784)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1513)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:64)
at 
org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:315)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:152)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:145)
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
at hudson.remoting.Request$2.run(Request.java:336)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
at ..remote call to H10(Native Method)
at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1537)
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)
at hudson.remoting.Channel.call(Channel.java:822)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145)
at sun.reflect.GeneratedMethodAccessor465.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131)
at com.sun.proxy.$Proxy96.execute(Unknown Source)
at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:804)
... 11 more
ERROR: null
Retrying after 10 seconds
 > 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 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 c8748d221f8265c16e37383e8b3f1572bb613083 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2750:
--

Testing JIRA OOZIE-2750

Cleaning local git workspace

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-1887) Remove the utils dir

[Kevin Trieu (JIRA)]

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

Kevin Trieu updated OOZIE-1887:
---
Attachment: OOZIE-1887.001.patch

Here you go! :)

> Remove the utils dir
> 
>
> Key: OOZIE-1887
> URL: https://issues.apache.org/jira/browse/OOZIE-1887
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Robert Kanter
>Assignee: Kevin Trieu
>  Labels: newbie
> Attachments: OOZIE-1887.001.patch
>
>
> We should remove the utils directory, it contains some sql files that haven't 
> been updated in 3 years and are no longer used in favor of the ooziedb.sh 
> script.  They may confuse users who assume they should be used.
> https://github.com/apache/oozie/tree/master/utils



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Grant Sohn (JIRA)]

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

Grant Sohn updated OOZIE-2750:
--
Attachment: OOZIE-2750.5.patch

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch, OOZIE-2750.5.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Got alerts in ambari after install oozie HA in kerberos env.

[Dongying Jiao]

Hi:
I installed oozie HA in kerberos cluster according to document in HDP
website. But I got alerts from ambari UI for Oozie Server Status:
Execution of 'source /usr/oozie-server/conf/oozie-env.sh ; oozie admin
-oozie http://node2:11000/oozie -status' returned 255. Error: IO_ERROR :
java.io.IOException: Error while connecting Oozie server. No of retries =
1. Exception = Could not authenticate, Authentication failed, status: 403,
message: Forbidden.

3 nodes in my cluster, node1 is for oozie load balancer, node2 and node3
are oozie servers. I have merged spengo keytab in node1 to node2 and node3,
and change oozie.authentication.kerberos.principal to use Load balancer
Principal.

It is strange that getting node2 status command failed as the alert, but if
I first get node1 status and then get node2 status, it can be successful.
See output:

[oozie@node2 root]$ oozie admin -oozie http://*node2*:11000/oozie -status
Error: IO_ERROR : java.io.IOException: Error while connecting Oozie server.
No of retries = 1. Exception = Could not authenticate, Authentication
failed, status: 403, message: Forbidden

[oozie@node2 root]$ oozie admin -oozie http://*node1*:11000/oozie -status
System mode: NORMAL

[oozie@node2 root]$ oozie admin -oozie http://*node2*:11000/oozie -status
System mode: NORMAL

Could you please help?
Thank you.

Best Regards,
Dong Ying

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

[Apache Jenkins Server]

See 


--
[...truncated 1.37 MB...]
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/org/apache/oozie/cli/class-use/CLIParser.Command.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/org/apache/oozie/cli/package-summary.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/org/apache/oozie/cli/package-tree.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/org/apache/oozie/cli/CLIParser.Command.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/org/apache/oozie/cli/package-frame.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/org/apache/oozie/cli/package-use.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/AppType.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/BuildInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/OozieClient.MapClientCallable.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/SLAEvent.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/JMSConnectionInfo.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/AuthOozieClient.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/WorkflowAction.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/SLAEvent.SlaAppType.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/CoordinatorAction.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/OozieClient.ClientCallable.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/OozieClient.Instrumentation.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/OozieClient.SYSTEM_MODE.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/OozieClient.Metrics.Timer.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/SLAEvent.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/message/EventMessage.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/message/JobMessage.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/message/WorkflowJobMessage.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/message/CoordinatorActionMessage.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/message/SLAMessage.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/SLAEvent.EventStatus.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/Event.html
 longer than 100 characters.
[WARNING] Entry: 
oozie-4.4.0-SNAPSHOT/embedded-oozie-server/webapp/docs/client/apidocs/src-html/org/apache/oozie/client/event/Event.MessageType.html
 longer than 100 characters.
[WARNING] 

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2817:
--

Testing JIRA OOZIE-2817

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:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [core].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
.{color:green}+1{color} There are no new bugs found in [client].
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 54
{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/3677/

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2540) Create a PySpark example

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2540:
--

+1  This should be useful.

> Create a PySpark example
> 
>
> Key: OOZIE-2540
> URL: https://issues.apache.org/jira/browse/OOZIE-2540
> Project: Oozie
>  Issue Type: Task
>  Components: examples
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
> Fix For: 5.0.0
>
> Attachments: OOZIE-2540-00.patch
>
>
> Now that we have PySpark working correctly in the Spark Action, we should 
> make an example that runs a PySpark job to give users an example of how to do 
> it.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2817) Increase test case stability in pre-commit job

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2817:
--

This is a great idea.  It should be helpful to get more green runs from 
Jenkins.  Some minor things:
# Can you run [shellcheck|https://github.com/koalaman/shellcheck] on this and 
fix the (reasonable) things it finds?
# Can you have it report what the flakey tests were (i.e. they failed the first 
run but passed on the rerun)?  Otherwise, your changes will hide the flakey 
tests and we won't have a good idea of which tests are flakey anymore.

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 54705: OOZIE-1770: Create Oozie Application Master for YARN

[Robert Kanter]

> On Jan. 6, 2017, 7:19 a.m., Robert Kanter wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
> > Lines 1143-1148 (original), 991-1001 (patched)
> > 
> >
> > Instead of doing this (which I know is equivalent to what we currently 
> > do), would it better to call check(...) instead?  I think it 
> > handles stuff better (e.g. fallback to data file, etc).  Or maybe we can 
> > extract out the common code into a new method and have them both call that, 
> > if we don't want all of check(...) here.
> 
> Peter Bacsko wrote:
> You mean to call check() when the Launcher is already running?

Hmm, I don't remember what I was getting at here; let's ignore this for now.


> On Jan. 6, 2017, 7:19 a.m., Robert Kanter wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
> > Lines 1113-1117 (patched)
> > 
> >
> > Do we need this?
> 
> Peter Bacsko wrote:
> We might not need -Dlog4j.debug (although I think it's useful when we 
> have logging problems) but the rest was copy-pasted from MRApps.java or 
> already existed (your early code). The hadoop.root.logger and 
> hadoop.root.logfile props are definitely necessary, perhaps the root loggers 
> could be configurable.

The other stuff sounds fine then, but the log4j.debug=true turns on 
debug logging for Log4j itself, right?  I don't think we need that.


> On Jan. 6, 2017, 7:19 a.m., Robert Kanter wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/JavaActionExecutor.java
> > Lines 1115 (patched)
> > 
> >
> > Does this mean the launcher logs can't be larger than 1GB?
> 
> Peter Bacsko wrote:
> I don't know - this value was already here :)

It looks like this gets passed to the log4j config for the container.  It 
essentially sets the max filesize for when to rollover the log file.  Looking 
at how MRApps sets it 
(https://github.com/apache/hadoop/blob/f67237cbe7bc48a1b9088e990800b37529f1db2a/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-common/src/main/java/org/apache/hadoop/mapreduce/v2/util/MRApps.java#L710)
 to MRJobConfig.MR_AM_LOG_KB, which is 0 by default (indicating no rollover).  
Given that, I'm thinking we should set this to 0 so we don't rollover - I'm not 
sure how well Yarn will handle a rolled over log file.


> On Jan. 6, 2017, 7:19 a.m., Robert Kanter wrote:
> > core/src/main/java/org/apache/oozie/action/hadoop/SparkActionExecutor.java
> > Lines 156-158 (patched)
> > 
> >
> > We shouldn't need the MR jars in the Spark Action :)
> 
> Peter Cseh wrote:
> Oozie's SparkExample needs MR jars on the classpath.

That's surprising, but okay.


> On Jan. 6, 2017, 7:19 a.m., Robert Kanter wrote:
> > core/src/test/java/org/apache/oozie/action/hadoop/TestJavaActionExecutor.java
> > Lines 1787-1821 (original), 1640-1674 (patched)
> > 
> >
> > What's the plan here?
> 
> Peter Bacsko wrote:
> Perhaps we don't need this test anymore.
> 
> I'm not entirely familiar with MapReduce ACLs but I think it's related to 
> the LauncherMapper. But we don't have a mapper anymore, but a standalone AM. 
> Do we still care about MR ACLs?

I'm not either, but it sounds like this doesn't apply anymore so we should 
delete it.


- Robert


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


On Jan. 23, 2017, 11:43 a.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/54705/
> ---
> 
> (Updated Jan. 23, 2017, 11:43 a.m.)
> 
> 
> Review request for oozie, Purshotam Shah, Robert Kanter, and Rohini 
> Palaniswamy.
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> Replacing the launcher MR job with a launcher AM
> 
> 
> Diffs
> -
> 
>   client/pom.xml f99366c90887a5a45f3942291c90e1cdbfd84b3f 
>   client/src/main/java/org/apache/oozie/cli/OozieCLI.java 
> 6e30d7eb667fe74440281fab3ca06c9f4df7bcf7 
>   client/src/main/java/org/apache/oozie/client/XOozieClient.java 
> 8538ec7c742cc013f7c18eaff3ecf61c2835cc8a 
>   core/pom.xml 1dd104581ccab7976d788b674d2200e48a70c27f 
>   core/src/main/java/org/apache/oozie/WorkflowJobBean.java 
> 55d79a5d5e5e4efab9eb832e9341a16bcf8959cc 
>   core/src/main/java/org/apache/oozie/action/ActionExecutor.java 
> 

[jira] [Updated] (OOZIE-2813) Remove tabs and trailing whitespaces from oozie-defaul.xml

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2813:
--
Attachment: OOZIE-2813-001.patch

> Remove tabs and trailing whitespaces from oozie-defaul.xml
> --
>
> Key: OOZIE-2813
> URL: https://issues.apache.org/jira/browse/OOZIE-2813
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>  Labels: newbie
> Attachments: OOZIE-2813-001.patch
>
>
> oozie-default.xml has a buch of tab characters and trailing whitespaces in it.
> >> [9] 09:41 : oozie (master) :: grep "\t" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   75
> >> [10] 09:41 : oozie (master) :: grep " $" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   17
> Trailing whitespaces should be removed, while tabs have to replaced with 
> spaces.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Assigned] (OOZIE-2813) Remove tabs and trailing whitespaces from oozie-defaul.xml

[Peter Cseh (JIRA)]

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

Peter Cseh reassigned OOZIE-2813:
-

Assignee: Peter Cseh

> Remove tabs and trailing whitespaces from oozie-defaul.xml
> --
>
> Key: OOZIE-2813
> URL: https://issues.apache.org/jira/browse/OOZIE-2813
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>  Labels: newbie
> Attachments: OOZIE-2813-001.patch
>
>
> oozie-default.xml has a buch of tab characters and trailing whitespaces in it.
> >> [9] 09:41 : oozie (master) :: grep "\t" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   75
> >> [10] 09:41 : oozie (master) :: grep " $" 
> >> core/src/main/resources/oozie-default.xml |wc -l
>   17
> Trailing whitespaces should be removed, while tabs have to replaced with 
> spaces.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Updated] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

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

Peter Cseh updated OOZIE-2817:
--
Attachment: OOZIE-2817-001.patch

> Increase test case stability in pre-commit job
> --
>
> Key: OOZIE-2817
> URL: https://issues.apache.org/jira/browse/OOZIE-2817
> Project: Oozie
>  Issue Type: Bug
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2817-001.patch
>
>
> We could collect the failed tests and rerun them in the pre-commit hook.
> They will still fail if they are broken, but they'll probably pass if they 
> are just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2817) Increase test case stability in pre-commit job

[Peter Cseh (JIRA)]

Peter Cseh created OOZIE-2817:
-

 Summary: Increase test case stability in pre-commit job
 Key: OOZIE-2817
 URL: https://issues.apache.org/jira/browse/OOZIE-2817
 Project: Oozie
  Issue Type: Bug
Reporter: Peter Cseh
Assignee: Peter Cseh


We could collect the failed tests and rerun them in the pre-commit hook.
They will still fail if they are broken, but they'll probably pass if they are 
just flaky.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Apache Jenkins Server]

See 

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

[Apache Jenkins Server]

See 


--
Started by timer
[EnvInject] - Loading node environment variables.
Building remotely on H1 (Hadoop) 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 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 e62ffc39e25c29917e76349aaddce3222089adb8 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f e62ffc39e25c29917e76349aaddce3222089adb8
 > git rev-list e62ffc39e25c29917e76349aaddce3222089adb8 # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson1797418743347517601.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  
0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
curl: (56) SSL read: error::lib(0):func(0):reason(0), errno 104
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Assigned] (OOZIE-1887) Remove the utils dir

[Robert Kanter (JIRA)]

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

Robert Kanter reassigned OOZIE-1887:


Assignee: Kevin Trieu

> Remove the utils dir
> 
>
> Key: OOZIE-1887
> URL: https://issues.apache.org/jira/browse/OOZIE-1887
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 4.0.0
>Reporter: Robert Kanter
>Assignee: Kevin Trieu
>  Labels: newbie
>
> We should remove the utils directory, it contains some sql files that haven't 
> been updated in 3 years and are no longer used in favor of the ooziedb.sh 
> script.  They may confuse users who assume they should be used.
> https://github.com/apache/oozie/tree/master/utils



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2753) Update Docs for Jetty Tomcat changes

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2753:
--

The {{oozie-setup.sh prepare-war \[-secure\]}} command doesn't work anymore 
because of the Jetty changes, right?  I see that you removed it from the docs, 
but it's still actually in the {{oozie-setup.sh}} script.  I think we should 
clean that up too while we're here. 

> Update Docs for Jetty Tomcat changes
> 
>
> Key: OOZIE-2753
> URL: https://issues.apache.org/jira/browse/OOZIE-2753
> Project: Oozie
>  Issue Type: Sub-task
>  Components: docs
>Affects Versions: 5.0.0
>Reporter: Robert Kanter
>Assignee: Attila Sasvari
> Fix For: 5.0.0
>
> Attachments: OOZIE-2753-01.patch, OOZIE-2753-02.patch
>
>
> Update the docs based on the changes for Jetty and Tomcat (OOZIE-2317 and 
> child JIRAs).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Resolved] (OOZIE-2304) update test-patch to work with p0 and p1

[Robert Kanter (JIRA)]

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

Robert Kanter resolved OOZIE-2304.
--
Resolution: Duplicate

> update test-patch to work with p0 and p1
> 
>
> Key: OOZIE-2304
> URL: https://issues.apache.org/jira/browse/OOZIE-2304
> Project: Oozie
>  Issue Type: Test
>  Components: tests
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> test-patch currently uses {{-p0}}, which means that it requires patches to be 
> generated without a prefix ({{\--no-prefix}}).  However, ReviewBoard uses 
> {{-p1}}, which means that it requires patches to use a prefix.  This makes 
> posting a patch annoying because you need to generate it twice (with and 
> without {{\--no-prefix}}) so that you can upload it to JIRA and to 
> ReviewBoard.  
> It would be great if test-patch could use either {{-p0}} or {{-p1}} depending 
> on the patch so that you'd only have to generate 1 patch.  And when not using 
> ReviewBoard, this would also be more flexible as new contributors sometimes 
> post patches with a prefix.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2750) Spelling errors in the log messages and exception messages

[Robert Kanter (JIRA)]

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

Robert Kanter commented on OOZIE-2750:
--

+1

[~grant.sohn], looks like it doesn't apply cleanly anymore.  Can you rebase it?

> Spelling errors in the log messages and exception messages
> --
>
> Key: OOZIE-2750
> URL: https://issues.apache.org/jira/browse/OOZIE-2750
> Project: Oozie
>  Issue Type: Bug
>  Components: client, core, tools
>Reporter: Grant Sohn
>Assignee: Grant Sohn
>Priority: Trivial
> Attachments: OOZIE-2750.1.patch, OOZIE-2750.2.patch, 
> OOZIE-2750.3.patch, OOZIE-2750.4.patch
>
>
> Found a bunch of spelling errors in the log messages like 'ugprade' for 
> 'upgrade' and 'kerberoes' for 'kerberos'.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

[Apache Jenkins Server]

See 


Changes:

[rkanter] OOZIE-2811 Add support for filtering out properties from

[rkanter] OOZIE-807 Docs can be explicit about multiple sub-workflow definitions

--
[...truncated 945.82 KB...]
[INFO] Copying org.eclipse.jdt.core-3.8.2.v20130121.jar to 

[INFO] Copying quartz-2.1.7.jar to 

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

[INFO] Copying mockito-all-1.10.19.jar to 

[INFO] Copying guice-servlet-3.0.jar to 

[INFO] Copying jung-algorithms-2.0.1.jar to 

[INFO] Copying libfb303-0.9.2.jar to 

[INFO] Copying stringtemplate-3.2.1.jar to 

[INFO] Copying stax-api-1.0-2.jar to 

[INFO] Copying hive-metastore-1.2.0.jar to 

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

[INFO] Copying calcite-core-1.2.0-incubating.jar to 

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

[INFO] Copying hive-service-1.2.0.jar to 

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

[INFO] Copying curator-framework-2.5.0.jar to 

[INFO] Copying servlet-api-2.5.jar to 

[INFO] Copying libthrift-0.9.2.jar to 

[INFO] Copying antlr-runtime-3.4.jar to 

[INFO] Copying geronimo-jms_1.1_spec-1.1.1.jar to 

[INFO] Copying ivy-2.4.0.jar to 

[INFO] Copying metrics-core-3.0.2.jar to 

[INFO] Copying jackson-core-asl-1.9.13.jar to 

[INFO] Copying commons-jexl-2.1.1.jar to 

[INFO] Copying commons-pool-1.5.4.jar to 

[INFO] Copying jaxb-impl-2.2.3-1.jar to 

[INFO] Copying jets3t-0.9.0.jar to 

[INFO] Copying datanucleus-rdbms-3.2.9.jar to 

[INFO] Copying hive-common-1.2.0.jar to 

[INFO] Copying snappy-java-1.0.4.1.jar to 

[jira] [Commented] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2816:
--

Testing JIRA OOZIE-2816

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 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: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{color} There are no new bugs found in total.
.{color:green}+1{color} There are no new bugs found in [client].
.{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/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 [core].
.{color:green}+1{color} There are no new bugs found in 
[hadooplibs/hadoop-utils-2].
{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/3675/

> Strip out the first command word from Sqoop action if its "sqoop"
> -
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Attachments: OOZIE-2816.000.patch
>
>
> A [sorta 
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
>  user error is to specify the command part of the sqoop action in the style 
> of the CLI: "sqoop import …" instead of just the required "import …". This 
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first 
> command token if its "sqoop".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Commented] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Andras Piros (JIRA)]

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

Andras Piros commented on OOZIE-2816:
-

Hi [~qwertymaniac],

can you post a ReviewBoard review request?

Thanks!

> Strip out the first command word from Sqoop action if its "sqoop"
> -
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Attachments: OOZIE-2816.000.patch
>
>
> A [sorta 
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
>  user error is to specify the command part of the sqoop action in the style 
> of the CLI: "sqoop import …" instead of just the required "import …". This 
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first 
> command token if its "sqoop".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Re: Review Request 57107: OOZIE-2815 oozie not always display job log

[András Piros]

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




core/src/main/java/org/apache/oozie/BaseEngine.java
Lines 176-182 (patched)


Code duplication: can you just please use template method pattern?



core/src/main/java/org/apache/oozie/BaseEngine.java
Line 192 (original), 197-203 (patched)


Code duplication: can you just please use template method pattern?



core/src/main/java/org/apache/oozie/BaseEngine.java
Line 204 (original), 216-221 (patched)


Code duplication: can you just please use template method pattern?



core/src/main/java/org/apache/oozie/util/AuthUrlClient.java
Lines 44 (patched)


Would be better to name it with the unit of measure, e.g. 
`SERVER_SERVER_CONNECTION_TIMEOUT_SECONDS`.



core/src/main/java/org/apache/oozie/util/AuthUrlClient.java
Lines 132 (patched)


Should use a default timeout if configuration key is not present.



core/src/main/java/org/apache/oozie/util/XLogAuditStreamer.java
Lines 39 (patched)


Would be nice to have a sane default value.



core/src/main/java/org/apache/oozie/util/XLogAuditStreamer.java
Lines 68-77 (patched)


Parameter `writtenBytes` is not used. Is it intentional? If so, please 
rename it, like `byteCountIgnored`.

Moreover, please rename the method to e.g. `checkAndFlush()` to better 
reflect what it actually does.



core/src/main/java/org/apache/oozie/util/XLogFilter.java
Lines 251 (patched)


Please rename to `calculateAndCheckDates()`.



core/src/main/java/org/apache/oozie/util/XLogFilter.java
Lines 302-305 (patched)


This check should come just after `startDate` and `endDate` have both been 
set.



core/src/main/java/org/apache/oozie/util/XLogStreamer.java
Lines 62-64 (patched)


Since the parameter `logFile` shadows the field `logFile`, and the field 
`logFile` has already been set, no effect is taken by that, breaking the 
functionality.

Either move that check-and-set back to its original place or remove it 
completely.



core/src/main/java/org/apache/oozie/util/XLogStreamer.java
Lines 318-327 (patched)


Parameter `writtenBytes` is not used. Is it intentional? If so, please 
rename it, like `byteCountIgnored`.

Moreover, please rename the method to e.g. `checkAndFlush()` to better 
reflect what it actually does.



core/src/main/java/org/apache/oozie/util/XLogStreamer.java
Lines 334-335 (patched)


Using `String.format()`, a `StringBuilder` instance, or Guava's 
`Objects.toStringHelper()` would be way sexier.



core/src/main/resources/oozie-default.xml
Lines 207 (patched)


`oozie.service.XLogStreamingService.audit.buffer.lineCount` would be a 
better name.



core/src/main/resources/oozie-default.xml
Lines 2235 (patched)


`oozie.server.connection.timeout.seconds` would be a better name.



core/src/main/resources/oozie-default.xml
Lines 2236 (patched)


I don't see how milliseconds could be useful here - setting to `180` would 
be better.



core/src/test/java/org/apache/oozie/service/TestXLogStreamingService.java
Lines 407 (patched)


Extracting to an `int fifteenHoursInSeconds` local variable would be more 
helpful.



core/src/test/java/org/apache/oozie/util/TestLogStreamer.java
Lines 347 (patched)


It would be useful to store here the original `XLogService.LOG4J_FILE` and 
then set it back in `tearDown()` for subsequent test runs.


- András Piros


On March 8, 2017, 6:56 p.m., Purshotam Shah wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/57107/
> ---
> 
> (Updated March 8, 2017, 6:56 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2815
> https://issues.apache.org/jira/browse/OOZIE-2815
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> OOZIE-2815 oozie not always display job log
> 
> 
> Diffs
> -
> 
> 

[jira] [Updated] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Harsh J (JIRA)]

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

Harsh J updated OOZIE-2816:
---
Attachment: OOZIE-2816.000.patch

> Strip out the first command word from Sqoop action if its "sqoop"
> -
>
> Key: OOZIE-2816
> URL: https://issues.apache.org/jira/browse/OOZIE-2816
> Project: Oozie
>  Issue Type: Bug
>  Components: action
>Affects Versions: 4.3.0
>Reporter: Harsh J
>Assignee: Harsh J
>Priority: Trivial
> Attachments: OOZIE-2816.000.patch
>
>
> A [sorta 
> popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
>  user error is to specify the command part of the sqoop action in the style 
> of the CLI: "sqoop import …" instead of just the required "import …". This 
> causes the Sqoop action to predictably fail with:
> {code}
> No such sqoop tool: sqoop. See 'sqoop help'.
> Intercepting System.exit(1)
> {code}
> A simple enhancement can prevent this burden on user. We can skip the first 
> command token if its "sqoop".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

[jira] [Created] (OOZIE-2816) Strip out the first command word from Sqoop action if its "sqoop"

[Harsh J (JIRA)]

Harsh J created OOZIE-2816:
--

 Summary: Strip out the first command word from Sqoop action if its 
"sqoop"
 Key: OOZIE-2816
 URL: https://issues.apache.org/jira/browse/OOZIE-2816
 Project: Oozie
  Issue Type: Bug
  Components: action
Affects Versions: 4.3.0
Reporter: Harsh J
Assignee: Harsh J
Priority: Trivial


A [sorta 
popular|https://www.google.com/search?q=%22No+such+sqoop+tool:+sqoop%22+oozie&*]
 user error is to specify the command part of the sqoop action in the style of 
the CLI: "sqoop import …" instead of just the required "import …". This causes 
the Sqoop action to predictably fail with:

{code}
No such sqoop tool: sqoop. See 'sqoop help'.
Intercepting System.exit(1)
{code}

A simple enhancement can prevent this burden on user. We can skip the first 
command token if its "sqoop".



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)