date:20160825

Re: Review Request 51137: OOZIE-2632 Provide database dump/load functionality to make database migration easier

2016-08-25 Thread Robert Kanter


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




tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java (line 170)


better error message



tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java (line 62)


Given that setUp, tearDown, OozieDBImportCLI, and the test itself all use 
Services, we need to be very careful in here not to accidently create a new 
Services if there's already an existing one running.  That could cause all 
kinds of weird problems for other tests.

You'll be needing to add some try-finally blocks throughout this class.  
Yes, I know that's ugly :)


- Robert Kanter


On Aug. 25, 2016, 2:58 p.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51137/
> ---
> 
> (Updated Aug. 25, 2016, 2:58 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2632
> https://issues.apache.org/jira/browse/OOZIE-2632
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> When there is a need to change the database under Oozie one has to submit all 
> the workflows again or migrate the data manually which is not easy because of 
> the binary blobs stored in the DB. 
> oozie-setup.sh could have a db export/import command that would save the 
> contents of the Db to a file and read it back from it. Functionality added 
> with some tests. The database is dumped using GSON to json files and zipped 
> to a single file to use less disk space.
> 
> 
> Diffs
> -
> 
>   distro/src/main/bin/oozie-setup.ps1 
> ca89b8838c8f43b659605b6e4d83cdefa530c21c 
>   distro/src/main/bin/oozie-setup.sh 3b6a6431fef007e77f3b3d99f4e98807e1808c11 
>   pom.xml 9e06e89fdaceb5ac53d12bef2e624f755fa7f350 
>   tools/pom.xml 114ba8ee8dd2d531837e2ae4097b7ea3c0419eed 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java 
> 8b3e93918d595d0235090f4dafb5f04158d45398 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_ac.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_bna.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_bnj.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_ca.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_cj.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_slareg.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_slasum.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_sysinfo.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_wf.json PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/51137/diff/
> 
> 
> Testing
> ---
> 
> I've tested migrating between MySQL, Derby and Oracle. After restarting 
> Oozie, the workflows/coordinators kept running and their status was updated 
> properly.
> 
> 
> Thanks,
> 
> Peter Cseh
> 
>

[jira] [Assigned] (OOZIE-2041) Add an admin command to run the PurgeXCommand

2016-08-25 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna reassigned OOZIE-2041:
-

Assignee: Abhishek Bafna

> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>Assignee: Abhishek Bafna
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.  
> We can add a new admin command to run this.  e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we 
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either 
> it's already running (i.e. the user sent it twice) or if the scheduled 
> PurgeService is already running it.  On top of that, we may need extra 
> consideration for HA setups where we currently only run it on the leader.  
> We should probably also have a to not schedule the PurgeService in ooize-site 
> for users who only want to run it manually.



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

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

2016-08-25 Thread Apache Jenkins Server

See 

--
[...truncated 6243 lines...]
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-tools ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @

[jira] [Commented] (OOZIE-2616) Add Tez profile for Hive and Pig sharelibs

2016-08-25 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2616:
--

Testing JIRA OOZIE-2616

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:green}+1{color} the patch does not introduce any line longer than 
132
.{color:red}-1{color} the patch does not add/modify any testcase
{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: 1798
{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/3241/

> Add Tez profile for Hive and Pig sharelibs
> --
>
> Key: OOZIE-2616
> URL: https://issues.apache.org/jira/browse/OOZIE-2616
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Thomas Poepping
> Attachments: OOZIE-2616-1.patch, OOZIE-2616-2.patch
>
>
> More recent versions of Hive and Pig depend on Tez as their default execution 
> engine. As the sharelib for those applications stands today, those 
> applications are unable to run Tez jobs. This patch adds an optional profile 
> to the root pom that will include the proper Tez dependencies into those 
> sharelibs, while excluding problematic jars to keep the sharelibs from having 
> classpath duplication issues. *Note*: this patch will only be required for 
> those clients who specify their own, newer versions of Hive or Pig. This 
> change is not required for the current supported versions of those 
> applications (hence why the profile is off by default).



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

[jira] [Updated] (OOZIE-2616) Add Tez profile for Hive and Pig sharelibs

2016-08-25 Thread Thomas Poepping (JIRA)


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

Thomas Poepping updated OOZIE-2616:
---
Attachment: OOZIE-2616-2.patch

Added wiki documentation. Appreciate comments.

> Add Tez profile for Hive and Pig sharelibs
> --
>
> Key: OOZIE-2616
> URL: https://issues.apache.org/jira/browse/OOZIE-2616
> Project: Oozie
>  Issue Type: Improvement
>Affects Versions: trunk
>Reporter: Thomas Poepping
> Attachments: OOZIE-2616-1.patch, OOZIE-2616-2.patch
>
>
> More recent versions of Hive and Pig depend on Tez as their default execution 
> engine. As the sharelib for those applications stands today, those 
> applications are unable to run Tez jobs. This patch adds an optional profile 
> to the root pom that will include the proper Tez dependencies into those 
> sharelibs, while excluding problematic jars to keep the sharelibs from having 
> classpath duplication issues. *Note*: this patch will only be required for 
> those clients who specify their own, newer versions of Hive or Pig. This 
> change is not required for the current supported versions of those 
> applications (hence why the profile is off by default).



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

[jira] [Commented] (OOZIE-2615) Flaky tests TestCoordActionsKillXCommand.testActionKillCommandActionNumbers and testActionKillCommandDate

2016-08-25 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2615:
--

Testing JIRA OOZIE-2615

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: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: 1798
{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/3240/

> Flaky tests TestCoordActionsKillXCommand.testActionKillCommandActionNumbers 
> and testActionKillCommandDate 
> --
>
> Key: OOZIE-2615
> URL: https://issues.apache.org/jira/browse/OOZIE-2615
> Project: Oozie
>  Issue Type: Bug
>  Components: tests
>Reporter: Peter Bacsko
>Assignee: Peter Bacsko
>Priority: Minor
> Attachments: OOZIE-2615-001.patch
>
>
> Two test cases are unstable because StatusTransitService might change the 
> coord job status.
> {code:title=testActionKillCommandDate|borderStyle=solid}
> 08:15:16,122 [pool-3063-thread-2] TRACE CoordStatusTransitXCommand:529 - 
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] 
> JOB[000-160708081515125-oozie-root-C] ACTION[-] Precondition check for 
> command [coord_status_transit] key [000-160708081515125-oozie-root-C]
> 08:15:16,122 [pool-3063-thread-2] DEBUG CoordStatusTransitXCommand:526 - 
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] 
> JOB[000-160708081515125-oozie-root-C] ACTION[-] Execute command 
> [coord_status_transit] key [000-160708081515125-oozie-root-C]
> 08:15:16,122 [pool-3063-thread-2]  INFO CoordStatusTransitXCommand:520 - 
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] 
> JOB[000-160708081515125-oozie-root-C] ACTION[-] Set coordinator job 
> [000-160708081515125-oozie-root-C] status to 'KILLED' from 'RUNNING'
> {code}
> {code:title=testActionKillCommandActionNumbers|borderStyle=solid}
> 08:15:13,886 [pool-3059-thread-2] TRACE CoordStatusTransitXCommand:529 - 
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] 
> JOB[000-160708081512561-oozie-root-C] ACTION[-] Precondition check for 
> command [coord_status_transit] key [000-160708081512561-oozie-root-C]
> 08:15:13,886 [pool-3059-thread-2] DEBUG CoordStatusTransitXCommand:526 - 
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] 
> JOB[000-160708081512561-oozie-root-C] ACTION[-] Execute command 
> [coord_status_transit] key [000-160708081512561-oozie-root-C]
> 08:15:13,886 [pool-3059-thread-2]  INFO CoordStatusTransitXCommand:520 - 
> USER[test] GROUP[testg] TOKEN[] APP[COORD-TEST] 
> JOB[000-160708081512561-oozie-root-C] ACTION[-] Set coordinator job 
> [000-160708081512561-oozie-root-C] status to 'RUNNINGWITHERROR' from 
> 'RUNNING'
> {code}



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

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

2016-08-25 Thread Apache Jenkins Server

See

[jira] [Commented] (OOZIE-2632) Provide database dump/load functionality to make database migration easier

2016-08-25 Thread Jaydeep Vishwakarma (JIRA)


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

Jaydeep Vishwakarma commented on OOZIE-2632:


[~gezapeti], I agree with the need of this jira, But solving approach is 
problematic. For smaller data size it will work perfect, But for large DB which 
you generally find in production environment , It is an overkill. 



> Provide database dump/load functionality to make database migration easier
> --
>
> Key: OOZIE-2632
> URL: https://issues.apache.org/jira/browse/OOZIE-2632
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2632.001.patch, OOZIE-2632.002.patch, 
> OOZIE-2632.003.patch
>
>
> When there is a need to change the database under Oozie one has to submit all 
> the workflows again or migrate the data manually which is not easy because of 
> the binary blobs stored in the DB. 
> oozie-setup.sh could have a db export/import command that would save the 
> contents of the Db to a file and read it back from it.



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

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

2016-08-25 Thread Apache Jenkins Server

See

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

2016-08-25 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 0754451daf5a7c3bdbc401bb245611a1da13731e 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 0754451daf5a7c3bdbc401bb245611a1da13731e
 > git rev-list 0754451daf5a7c3bdbc401bb245611a1da13731e # timeout=10
[oozie-trunk-find-patches-available] $ /bin/bash 
/tmp/hudson9157478255631000736.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  148k0  148k0 0   159k  0 --:--:-- --:--:-- --:--:--  159k
100  262k0  262k0 0   179k  0 --:--:--  0:00:01 --:--:--  179k
curl: (18) transfer closed with outstanding read data remaining
Could not retrieve available patches from JIRA
Build step 'Execute shell' marked build as failure

[jira] [Commented] (OOZIE-2647) input-events is always ignored for the first action (WF) of the coordinator if the instance is set to ${coord:current(-1)}

2016-08-25 Thread Purshotam Shah (JIRA)


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

Purshotam Shah commented on OOZIE-2647:
---

It will happen for -2 or -10, they fall out of the initial instance.

For -2
If your initial-instance is {{startTime}} and job start time is also 
{{startTime}}. So for 1st and 2nd action, current(-2) is nothing because they 
all out of initial-instance. 

> input-events is always ignored for the first action (WF) of the coordinator 
> if the instance is set to ${coord:current(-1)}
> --
>
> Key: OOZIE-2647
> URL: https://issues.apache.org/jira/browse/OOZIE-2647
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 4.1.0
> Environment: Oozie client build version: 4.1.0-cdh5.8.0
>Reporter: Burak Gursoy
> Attachments: 01-coordinator.xml, 01-job-state.txt, 
> 01-schedule-minus-one.txt, 01-workflow.xml, 02-coordinator.xml, 
> 02-job-state.txt, 02-schedule-zero.txt, 02-workflow.xml, job.properties
>
>
> Hi,
> We've noticed that if you have a definition like this in the coordinator.xml, 
> then the first action is always released and the existence of the data 
> dependency is never checked/verified. This only seems to happen with the 
> value "-1" and nothing else ("0", any other positive or negative value seems 
> to be fine).
> I currently don't have access to a more recent release, but I also couldn't 
> locate a bug related to this in here.
> {code}
>   
> 
>   ${coord:current(-1)}
> 
>   
> {code}



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

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

2016-08-25 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-2041:
--

Sure.  It's currently Unassigned.  Go ahead.

> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.  
> We can add a new admin command to run this.  e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we 
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either 
> it's already running (i.e. the user sent it twice) or if the scheduled 
> PurgeService is already running it.  On top of that, we may need extra 
> consideration for HA setups where we currently only run it on the leader.  
> We should probably also have a to not schedule the PurgeService in ooize-site 
> for users who only want to run it manually.



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

[jira] [Commented] (OOZIE-2632) Provide database dump/load functionality to make database migration easier

2016-08-25 Thread Peter Cseh (JIRA)


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

Peter Cseh commented on OOZIE-2632:
---

I've updated the RB.
Thanks for the suggestions [~rkanter]!
I've added a json with db.version info in it. I had to create the OOZIE_SYS 
table in the tests manually. The test will have to be updated upon db schema 
change.
If export fails for some reason (e.g. disk space runs out) now we're deleting 
the dump zip. 

[~rohini], [~puru] can you take a look at this?

> Provide database dump/load functionality to make database migration easier
> --
>
> Key: OOZIE-2632
> URL: https://issues.apache.org/jira/browse/OOZIE-2632
> Project: Oozie
>  Issue Type: New Feature
>Reporter: Peter Cseh
>Assignee: Peter Cseh
> Attachments: OOZIE-2632.001.patch, OOZIE-2632.002.patch, 
> OOZIE-2632.003.patch
>
>
> When there is a need to change the database under Oozie one has to submit all 
> the workflows again or migrate the data manually which is not easy because of 
> the binary blobs stored in the DB. 
> oozie-setup.sh could have a db export/import command that would save the 
> contents of the Db to a file and read it back from it.



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

Re: Review Request 51137: OOZIE-2632 Provide database dump/load functionality to make database migration easier

2016-08-25 Thread Peter Cseh


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

(Updated Aug. 25, 2016, 2:58 p.m.)


Review request for oozie.


Changes
---

- delete file if export fails
- fix test
- write out db version and check it before import.


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


Repository: oozie-git


Description
---

When there is a need to change the database under Oozie one has to submit all 
the workflows again or migrate the data manually which is not easy because of 
the binary blobs stored in the DB. 
oozie-setup.sh could have a db export/import command that would save the 
contents of the Db to a file and read it back from it. Functionality added with 
some tests. The database is dumped using GSON to json files and zipped to a 
single file to use less disk space.


Diffs (updated)
-

  distro/src/main/bin/oozie-setup.ps1 ca89b8838c8f43b659605b6e4d83cdefa530c21c 
  distro/src/main/bin/oozie-setup.sh 3b6a6431fef007e77f3b3d99f4e98807e1808c11 
  pom.xml 9e06e89fdaceb5ac53d12bef2e624f755fa7f350 
  tools/pom.xml 114ba8ee8dd2d531837e2ae4097b7ea3c0419eed 
  tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java 
8b3e93918d595d0235090f4dafb5f04158d45398 
  tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java PRE-CREATION 
  tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java PRE-CREATION 
  tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_ac.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_bna.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_bnj.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_ca.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_cj.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_slareg.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_slasum.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_sysinfo.json PRE-CREATION 
  tools/src/test/resources/dumpData/ooziedb_wf.json PRE-CREATION 

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


Testing
---

I've tested migrating between MySQL, Derby and Oracle. After restarting Oozie, 
the workflows/coordinators kept running and their status was updated properly.


Thanks,

Peter Cseh

[jira] [Commented] (OOZIE-2649) Can't override sub-workflow configuration property if defined in parent workflow XML

2016-08-25 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-2649:
--

Testing JIRA OOZIE-2649

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:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1798
.Tests failed: 2
.Tests errors: 0

.The patch failed the following testcases:

.  
testCoordStatus_Failed(org.apache.oozie.command.coord.TestCoordChangeXCommand)
.  
testConfigDefaultPropsToAction(org.apache.oozie.action.hadoop.TestMapReduceActionExecutor)

{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/3239/

> Can't override sub-workflow configuration property if defined in parent 
> workflow XML
> 
>
> Key: OOZIE-2649
> URL: https://issues.apache.org/jira/browse/OOZIE-2649
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2649.1.patch
>
>
> After OOZIE-2511, configuration property cannot overriden in sub-workflow.
> Unfortunately some scenarios concerning subworkflows are not covered with 
> tests.



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

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

2016-08-25 Thread Apache Jenkins Server

See 

--
[...truncated 6250 lines...]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-tools ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-tools ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-tools ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-tools ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-tools ---
[INFO] Reading assembly descriptor: ../src/main/assemblies/tools.xml
[WARNING] The following patterns were never triggered in this artifact 
exclusion filter:
o  '*:*:pom:*'

[INFO] Copying files to 

[WARNING] Assembly file: 

 is not a regular file (it may be a directory). It cannot be attached to the 
project build for installation or deployment.
[INFO] 
[INFO] 
[INFO] Building Apache Oozie MiniOozie 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-mini 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 3 resources
[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-mini ---
[INFO] Nothing to compile - all classes are up to date
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-mini ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-mini ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-mini ---
[INFO] 
[INFO] --- maven-assembly-plugin:2.2.1:single (default-cli) @ oozie-mini ---
[INFO] Reading assembly descriptor: src/main/assemblies/empty.xml
[INFO] 
[INFO] 
[INFO] Building Apache Oozie Distro 4.3.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ oozie-distro 
---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-resources-plugin:2.5:testResources (default-testResources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 3 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @ 
oozie-distro ---
[INFO] No sources to compile
[INFO] 
[INFO] --- maven-surefire-plugin:2.12.2:test (default-test) @ oozie-distro ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.3.1:jar (default-jar) @ oozie-distro ---
[INFO] Building jar: 

[INFO] 
[INFO] --- maven-site-plugin:2.0-beta-6:attach-descriptor (attach-descriptor) @ 
oozie-distro ---
[INFO] 
[INFO] --- maven-antrun-plugin:1.6:run

[jira] [Updated] (OOZIE-2649) Can't override sub-workflow configuration property if defined in parent workflow XML

2016-08-25 Thread Attila Sasvari (JIRA)


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

Attila Sasvari updated OOZIE-2649:
--
Attachment: OOZIE-2649.1.patch

> Can't override sub-workflow configuration property if defined in parent 
> workflow XML
> 
>
> Key: OOZIE-2649
> URL: https://issues.apache.org/jira/browse/OOZIE-2649
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Attila Sasvari
> Attachments: OOZIE-2649.1.patch
>
>
> After OOZIE-2511, configuration property cannot overriden in sub-workflow.
> Unfortunately some scenarios concerning subworkflows are not covered with 
> tests.



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

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

2016-08-25 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna commented on OOZIE-2041:
---

[~rkanter] Can I take up this issue?

> Add an admin command to run the PurgeXCommand
> -
>
> Key: OOZIE-2041
> URL: https://issues.apache.org/jira/browse/OOZIE-2041
> Project: Oozie
>  Issue Type: New Feature
>  Components: core
>Affects Versions: trunk
>Reporter: Robert Kanter
>
> Some users may find it useful to be able to run the PurgeXCommand on-demand.  
> We can add a new admin command to run this.  e.g.
> {noformat}
> oozie admin -purge
> {noformat}
> With no args, it can use the "older than" values from oozie-site, but we 
> could have it take some arguments to override those for the command.
> Another thing to worry about is making sure that we don't run this if either 
> it's already running (i.e. the user sent it twice) or if the scheduled 
> PurgeService is already running it.  On top of that, we may need extra 
> consideration for HA setups where we currently only run it on the leader.  
> We should probably also have a to not schedule the PurgeService in ooize-site 
> for users who only want to run it manually.



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

[jira] [Commented] (OOZIE-2650) Retry coord start on database exceptions

2016-08-25 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna commented on OOZIE-2650:
---

I think we can define a new error code instead of using {{E1304, "Duplicate 
bundle application coordinator name"}}

{code}
@Override
protected void verifyPrecondition() throws CommandException {
super.verifyPrecondition();
if (wfId != null) {
LOG.warn("Workflow is already submitted for Coord Action [{0}]", 
getParentId());
throw new CommandException(ErrorCode.E1304, getParentId());
}
}
{code}

> Retry coord start on database exceptions
> 
>
> Key: OOZIE-2650
> URL: https://issues.apache.org/jira/browse/OOZIE-2650
> Project: Oozie
>  Issue Type: Bug
>Reporter: Satish Subhashrao Saley
>Assignee: Satish Subhashrao Saley
> Attachments: OOZIE-2650-1.patch
>
>
> {code:title=CoordActionStartXCommand.java}
> updateList.add(new UpdateEntry(
> WorkflowJobQuery.UPDATE_WORKFLOW_PARENT_MODIFIED, 
> wfJob));
> updateList.add(new UpdateEntry(
> CoordActionQuery.UPDATE_COORD_ACTION_FOR_START, 
> coordAction));
> try {
> executor.executeBatchInsertUpdateDelete(insertList, 
> updateList, null);
> queue(new 
> CoordActionNotificationXCommand(coordAction), 100);
> if (EventHandlerService.isEnabled()) {
> generateEvent(coordAction, user, appName, 
> wfJob.getStartTime());
> }
> }
> catch (JPAExecutorException je) {
> throw new CommandException(je);
> }
> .
> ...
> 
>  finally {
> if (makeFail == true) { // No DB exception occurs
> 
> 
> 
> queue(new 
> CoordActionReadyXCommand(coordAction.getJobId()));
> }
> }
> {code}
> If there is any Database issue while starting coord action, we fail the coord 
> action. We should retry. 
> CoordActionStartXCommand submits workflow. Workflow gets linked to the coord 
> action if workflow submission succeeds. But if coord action update fails due 
> to database exception, recovery service should be able to recover it.



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

Re: Review Request 51137: OOZIE-2632 Provide database dump/load functionality to make database migration easier

2016-08-25 Thread Attila Sasvari


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




tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java (line 120)


It would worth to check whether Oozie database tables exist and they are 
empty. If they are not empty, then notify the user and fail the import process.

As of now, if we try to import the database twice, import will fail due key 
uniqueness violation (cannot insert it with the same primary key).

However, let's say we exported/dumped 2 different Oozie databases in 
different dump files. Then if the primary keys are different in the dump files, 
then we can populate a database that consists rows from both databases. It 
would be a quite unfortunate situation.

This extra validation can be implemented in a followup JIRA, if it is a 
huge modification.


- Attila Sasvari


On Aug. 16, 2016, 2:04 p.m., Peter Cseh wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/51137/
> ---
> 
> (Updated Aug. 16, 2016, 2:04 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2632
> https://issues.apache.org/jira/browse/OOZIE-2632
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> When there is a need to change the database under Oozie one has to submit all 
> the workflows again or migrate the data manually which is not easy because of 
> the binary blobs stored in the DB. 
> oozie-setup.sh could have a db export/import command that would save the 
> contents of the Db to a file and read it back from it. Functionality added 
> with some tests. The database is dumped using GSON to json files and zipped 
> to a single file to use less disk space.
> 
> 
> Diffs
> -
> 
>   distro/src/main/bin/oozie-setup.ps1 ca89b88 
>   distro/src/main/bin/oozie-setup.sh 3b6a643 
>   pom.xml 9e06e89 
>   tools/pom.xml 114ba8e 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBCLI.java 8b3e939 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBExportCLI.java 
> PRE-CREATION 
>   tools/src/main/java/org/apache/oozie/tools/OozieDBImportCLI.java 
> PRE-CREATION 
>   tools/src/test/java/org/apache/oozie/tools/TestDBLoadDump.java PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_ac.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_bna.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_bnj.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_ca.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_cj.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_slareg.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_slasum.json PRE-CREATION 
>   tools/src/test/resources/dumpData/ooziedb_wf.json PRE-CREATION 
> 
> Diff: https://reviews.apache.org/r/51137/diff/
> 
> 
> Testing
> ---
> 
> I've tested migrating between MySQL, Derby and Oracle. After restarting 
> Oozie, the workflows/coordinators kept running and their status was updated 
> properly.
> 
> 
> Thanks,
> 
> Peter Cseh
> 
>

[jira] [Commented] (OOZIE-2617) Read properties files in action configurations

2016-08-25 Thread Abhishek Bafna (JIRA)


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

Abhishek Bafna commented on OOZIE-2617:
---

+1 {{non-binding}}.

> Read properties files in action configurations
> --
>
> Key: OOZIE-2617
> URL: https://issues.apache.org/jira/browse/OOZIE-2617
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: trunk
>Reporter: Taklon Stephen Wu
>  Labels: patch
> Fix For: 4.3.0
>
> Attachments: OOZIE-2617-1.patch, OOZIE-2617-2.patch, 
> OOZIE-2617-3.patch
>
>
> Current logic of acton configuration only READ xml files within Oozie action 
> directory, but for pig and other applications, properties files are supported 
> and may be default configuration file format. To simplify the logic of 
> reusing these properties files when using Oozie with them, we add properties 
> file reading in action conf.



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

[jira] Subscription: Oozie Patch Available

2016-08-25 Thread jira

Issue Subscription
Filter: Oozie Patch Available (90 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2653  Close active connection to hcat server in fs action
https://issues.apache.org/jira/browse/OOZIE-2653
OOZIE-2650  Retry coord start on database exceptions
https://issues.apache.org/jira/browse/OOZIE-2650
OOZIE-2642  Extend TestSubWorkflowActionExecutor to the test if subworkflow 
action's parameter is properly set
https://issues.apache.org/jira/browse/OOZIE-2642
OOZIE-2641  rerunning an oozie coordinator job stucks on waiting
https://issues.apache.org/jira/browse/OOZIE-2641
OOZIE-2635  TimeZone.getTimeZone has performance issue.
https://issues.apache.org/jira/browse/OOZIE-2635
OOZIE-2632  Provide database dump/load functionality to make database migration 
easier
https://issues.apache.org/jira/browse/OOZIE-2632
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-2617  Read properties files in action configurations
https://issues.apache.org/jira/browse/OOZIE-2617
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-2606  Set spark.yarn.jars to fix Spark 2.0 with Oozie
https://issues.apache.org/jira/browse/OOZIE-2606
OOZIE-2588  Support getting credentials for same cluster hcat when credentials 
config is empty
https://issues.apache.org/jira/browse/OOZIE-2588
OOZIE-2585  Disable or remove test case 
TestPartitionDependencyManagerEhcache.testMemoryUsageAndSpeedOverflowToDisk and 
testMemoryUsageAndSpeed
https://issues.apache.org/jira/browse/OOZIE-2585
OOZIE-2584  Eliminate Thread.sleep() calls in TestMemoryLocks
https://issues.apache.org/jira/browse/OOZIE-2584
OOZIE-2583  oozie throws EL Exception when reference variable name containing 
dot
https://issues.apache.org/jira/browse/OOZIE-2583
OOZIE-2582  Populating external child Ids for action failures
https://issues.apache.org/jira/browse/OOZIE-2582
OOZIE-2573  dataset url  which contains spaces can not be handled rightly
https://issues.apache.org/jira/browse/OOZIE-2573
OOZIE-2572  SLA DURATION miss not shown when job is running for longer than 
expected time
https://issues.apache.org/jira/browse/OOZIE-2572
OOZIE-2571  Add scala.binary.version Maven property so that Scala 2.11 can be 
used
https://issues.apache.org/jira/browse/OOZIE-2571
OOZIE-2569  Adding yarn-site, core-site, hdfs-site and mapred-site into spark 
launcher 
https://issues.apache.org/jira/browse/OOZIE-2569
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-2552  Update ActiveMQ version for security and other fixes
https://issues.apache.org/jira/browse/OOZIE-2552
OOZIE-2538  Update HttpClient versions to close security vulnerabilities
https://issues.apache.org/jira/browse/OOZIE-2538
OOZIE-2534  Versioned action libs (similar to how SharedLibs works)
https://issues.apache.org/jira/browse/OOZIE-2534
OOZIE-2530  Remove jline from parent and sharelib pig pom
https://issues.apache.org/jira/browse/OOZIE-2530
OOZIE-2528  Print out environment variables in LauncherMapper
https://issues.apache.org/jira/browse/OOZIE-2528
OOZIE-2525  SchemaChecker fails with NPE
https://issues.apache.org/jira/browse/OOZIE-2525
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-2501  ZK reentrant lock doesn't work for few cases
https://issues.apache.org/jira/browse/OOZIE-2501
OOZIE-2500  -DtestJarSimple option mentioned in minioozie doc does not work
https://issues.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.apache.org/jira/browse/OOZIE-2499
OOZIE-2498  Oozie CallerId configuration for downstream components

Re: Review Request 51137: OOZIE-2632 Provide database dump/load functionality to make database migration easier

[jira] [Assigned] (OOZIE-2041) Add an admin command to run the PurgeXCommand

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

[jira] [Commented] (OOZIE-2616) Add Tez profile for Hive and Pig sharelibs

[jira] [Updated] (OOZIE-2616) Add Tez profile for Hive and Pig sharelibs

[jira] [Commented] (OOZIE-2615) Flaky tests TestCoordActionsKillXCommand.testActionKillCommandActionNumbers and testActionKillCommandDate

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

[jira] [Commented] (OOZIE-2632) Provide database dump/load functionality to make database migration easier

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

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

[jira] [Commented] (OOZIE-2647) input-events is always ignored for the first action (WF) of the coordinator if the instance is set to ${coord:current(-1)}

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[jira] [Commented] (OOZIE-2632) Provide database dump/load functionality to make database migration easier

Re: Review Request 51137: OOZIE-2632 Provide database dump/load functionality to make database migration easier

[jira] [Commented] (OOZIE-2649) Can't override sub-workflow configuration property if defined in parent workflow XML

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

[jira] [Updated] (OOZIE-2649) Can't override sub-workflow configuration property if defined in parent workflow XML

[jira] [Commented] (OOZIE-2041) Add an admin command to run the PurgeXCommand

[jira] [Commented] (OOZIE-2650) Retry coord start on database exceptions

Re: Review Request 51137: OOZIE-2632 Provide database dump/load functionality to make database migration easier

[jira] [Commented] (OOZIE-2617) Read properties files in action configurations

[jira] Subscription: Oozie Patch Available

22 matches

Site Navigation

Mail list logo

Footer information