[jira] Subscription: Oozie Patch Available

[jira]

Issue Subscription
Filter: Oozie Patch Available (47 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2100  Publish oozie-webapp artifact 
https://issues.apache.org/jira/browse/OOZIE-2100
OOZIE-2099  Add test-patch support for patches generated without --no-prefix
https://issues.apache.org/jira/browse/OOZIE-2099
OOZIE-2090  wf:lastErrorNode does not take into account transient errors with 
retries
https://issues.apache.org/jira/browse/OOZIE-2090
OOZIE-2088  Exponential retries for transient failures 
https://issues.apache.org/jira/browse/OOZIE-2088
OOZIE-2079  Notify when a coordinator action status becomes RUNNING
https://issues.apache.org/jira/browse/OOZIE-2079
OOZIE-2076  Sharelib usage improvement
https://issues.apache.org/jira/browse/OOZIE-2076
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
OOZIE-2055  PauseTransitService does not proceed forward if any job has issue 
https://issues.apache.org/jira/browse/OOZIE-2055
OOZIE-2051  Allows multiple default action configuration files per action
https://issues.apache.org/jira/browse/OOZIE-2051
OOZIE-2044  ssh action succeed with a not exists command which should be fail.
https://issues.apache.org/jira/browse/OOZIE-2044
OOZIE-2030  Configuration properties from global section is not getting set in 
Hadoop job conf when using sub-workflow action in Oozie workflow.xml 
https://issues.apache.org/jira/browse/OOZIE-2030
OOZIE-2027  Disable re-runs using the workflow directly if it has a parent
https://issues.apache.org/jira/browse/OOZIE-2027
OOZIE-1980  Sql error should not fail coord job
https://issues.apache.org/jira/browse/OOZIE-1980
OOZIE-1977  Display patch analysis issues
https://issues.apache.org/jira/browse/OOZIE-1977
OOZIE-1936  Queuedump command should display queue information for all server.
https://issues.apache.org/jira/browse/OOZIE-1936
OOZIE-1931  Admin command to print all locks held by server(s)
https://issues.apache.org/jira/browse/OOZIE-1931
OOZIE-1927  Use StoreStatusFilter for WorkflowsJobGetJPAExecutor 
https://issues.apache.org/jira/browse/OOZIE-1927
OOZIE-1922  MemoryLocksService fails if lock is acquired multiple times in same 
thread and released
https://issues.apache.org/jira/browse/OOZIE-1922
OOZIE-1918  ActionXCommand refactoring for code reuse
https://issues.apache.org/jira/browse/OOZIE-1918
OOZIE-1889  Convert NamedNativeQueries to JPQL
https://issues.apache.org/jira/browse/OOZIE-1889
OOZIE-1884  ZKJobsConcurrencyService.checkJobIdForServer fails if jobs length > 
7
https://issues.apache.org/jira/browse/OOZIE-1884
OOZIE-1876  use pom properties rather than specific version numbers in the pom 
files of hbaselibs, hcataloglibs, sharelib, etc 
https://issues.apache.org/jira/browse/OOZIE-1876
OOZIE-1860  Oozie job mapper launch fails due to null value returned from 
action file
https://issues.apache.org/jira/browse/OOZIE-1860
OOZIE-1855  TestPriorityDelayQueue#testPoll failed intermittently in Jenkins
https://issues.apache.org/jira/browse/OOZIE-1855
OOZIE-1829  URIHandlerService doesn't support URI schemes with query strings 
but no path segment
https://issues.apache.org/jira/browse/OOZIE-1829
OOZIE-1816  LogInfo uses action name instead of id
https://issues.apache.org/jira/browse/OOZIE-1816
OOZIE-1810  Workflow cannot get into Failed state when kill control node cannot 
resolve variable in message 
https://issues.apache.org/jira/browse/OOZIE-1810
OOZIE-1802  Support workflow action log
https://issues.apache.org/jira/browse/OOZIE-1802
OOZIE-1793  Improve find bugs reporting for Oozie
https://issues.apache.org/jira/browse/OOZIE-1793
OOZIE-1782  Workflow path not found is thrown as SC_UNAUTHORIZED
https://issues.apache.org/jira/browse/OOZIE-1782
OOZIE-1779  Add parent-id as a filter option
https://issues.apache.org/jira/browse/OOZIE-1779
OOZIE-1705  Enable gc logs and print thread id in logs
https://issues.apache.org/jira/browse/OOZIE-1705
OOZIE-1688  New configuration to specify server-server authentication type.
https://issues.apache.org/jira/browse/OOZIE-1688
OOZIE-1676  Instrumentation and Configuration over the REST API and Web UI 
should include all Oozie servers
https://issues.apache.org/jira/browse/OOZIE-1676
OOZIE-1654  Fix typo (inteval to interval)
https://issues.apache.org/jira/browse/OOZIE-1654
OOZIE-1638  Action retry does not use default retry max count.
https://issues.apache.org/jira/browse/OOZIE-1638
OOZIE-1636  OOZIE_SYS table engine should be innodb
https://issues.apache.org/jira/browse/OOZIE-1636
OOZIE

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

[Apache Jenkins Server]

See 

--
[...truncated 11851 lines...]
[INFO] Building Apache Oozie MiniOozie 4.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-mini ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-mini ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[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.2.0-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ oozie-distro 
---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
oozie-distro ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[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 (default) @ oozie-distro ---
[INFO] Executing tasks

main:
  [get] Getting: 
http://archive.apache.org/dist/tomcat/tomcat-6/v6.0.41/bin/apache-tomcat-6.0.41.tar.gz
  [get] To: 

.

[jira] [Commented] (OOZIE-2088) Exponential retries for transient failures

[Hadoop QA (JIRA)]

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

Hadoop QA commented on OOZIE-2088:
--

Testing JIRA OOZIE-2088

Cleaning local git workspace



{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:green}+1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any line longer than 
132
.{color:green}+1{color} the patch does adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT 
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} the patch does not seem to introduce new Javadoc 
warnings
{color:green}+1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:green}+1{color} patch compiles
.{color:green}+1{color} the patch does not seem to introduce new javac 
warnings
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA 
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:red}-1 TESTS{color}
.Tests run: 1560
.Tests failed: 0
.Tests errors: 1

.The patch failed the following testcases:

.  

{color:green}+1 DISTRO{color}
.{color:green}+1{color} distro tarball builds with the patch 


{color:red}*-1 Overall result, please check the reported -1(s)*{color}


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

.   https://builds.apache.org/job/oozie-trunk-precommit-build/2149/

> Exponential retries for transient failures 
> ---
>
> Key: OOZIE-2088
> URL: https://issues.apache.org/jira/browse/OOZIE-2088
> Project: Oozie
>  Issue Type: Improvement
>Reporter: pavan kumar kolamuri
>Assignee: pavan kumar kolamuri
> Attachments: OOZIE-2088.patch, OOZIE-2088v1.patch, OOZIE-2088v2.patch
>
>
> For transient failures there is retry mechanism but it is not exponential and 
> there is no separate config for changing the interval , it is linked with 
> oozie.service.ActionCheckerService.action.check.interval (Frequency at which 
> action checkservice will run) . Add separate config for retry interval and 
> add exponential retry mechanism. 



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

[jira] [Updated] (OOZIE-2088) Exponential retries for transient failures

[pavan kumar kolamuri (JIRA)]

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

pavan kumar kolamuri updated OOZIE-2088:

Attachment: OOZIE-2088v2.patch

> Exponential retries for transient failures 
> ---
>
> Key: OOZIE-2088
> URL: https://issues.apache.org/jira/browse/OOZIE-2088
> Project: Oozie
>  Issue Type: Improvement
>Reporter: pavan kumar kolamuri
>Assignee: pavan kumar kolamuri
> Attachments: OOZIE-2088.patch, OOZIE-2088v1.patch, OOZIE-2088v2.patch
>
>
> For transient failures there is retry mechanism but it is not exponential and 
> there is no separate config for changing the interval , it is linked with 
> oozie.service.ActionCheckerService.action.check.interval (Frequency at which 
> action checkservice will run) . Add separate config for retry interval and 
> add exponential retry mechanism. 



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

[jira] [Updated] (OOZIE-2101) all DAG workflow

[Grzegorz Chilkiewicz (JIRA)]

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

Grzegorz Chilkiewicz updated OOZIE-2101:

Description: 
i'd read documentation about Oozie,
it looks interesting, but i've a doubt:

first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
of actions."
so i assumed it can deal with any DAG, but documentation says it is limited to 
specific subset of DAGs, 
ie:  (DAG in ASCII art, directed top-down: )
1
.../.\
..2...\
./.\...\
3...4...5
.\...\./
..\...6
...\./
7
can't be expressed in Oozie workflow
(according to documentation: every join-node must join all branches of 
corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
am i wrong? / why it's so limited? / is it intentional?

//
//if join-node could just wait until all IN-edges are traversed,
//not necessary from any particular 'corresponding fork-node'
//it would work for all DAGs.
//


  was:
i'd read documentation about Oozie,
it looks interesting, but i've a doubt:

first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
of actions."
so i assumed it can deal with any DAG, but documentation says it is limited to 
specific subset of DAGs, 
ie:  (DAG in ASCII art, directed top-down:)
1
.../.\
..2...\
./.\...\
3...4...5
.\...\./
..\...6
...\./
7
can't be expressed in Oozie workflow
(according to documentation: every join-node must join all branches of 
corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
am i wrong? / why it's so limited? / is it intentional?

//
//if join-node could just wait until all IN-edges are traversed,
//not necessary from any particular 'corresponding fork-node'
//it would work for all DAGs.
//



> all DAG workflow
> 
>
> Key: OOZIE-2101
> URL: https://issues.apache.org/jira/browse/OOZIE-2101
> Project: Oozie
>  Issue Type: Wish
>Reporter: Grzegorz Chilkiewicz
>Priority: Minor
>
> i'd read documentation about Oozie,
> it looks interesting, but i've a doubt:
> first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
> of actions."
> so i assumed it can deal with any DAG, but documentation says it is limited 
> to specific subset of DAGs, 
> ie:  (DAG in ASCII art, directed top-down: )
> 1
> .../.\
> ..2...\
> ./.\...\
> 3...4...5
> .\...\./
> ..\...6
> ...\./
> 7
> can't be expressed in Oozie workflow
> (according to documentation: every join-node must join all branches of 
> corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
> am i wrong? / why it's so limited? / is it intentional?
> //
> //if join-node could just wait until all IN-edges are traversed,
> //not necessary from any particular 'corresponding fork-node'
> //it would work for all DAGs.
> //



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

[jira] [Updated] (OOZIE-2101) all DAG workflow

[Grzegorz Chilkiewicz (JIRA)]

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

Grzegorz Chilkiewicz updated OOZIE-2101:

Description: 
i'd read documentation about Oozie,
it looks interesting, but i've a doubt:

first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
of actions."
so i assumed it can deal with any DAG, but documentation says it is limited to 
specific subset of DAGs, 
ie:  (DAG in ASCII art, directed top-down:)
1
.../.\
..2...\
./.\...\
3...4...5
.\...\./
..\...6
...\./
7
can't be expressed in Oozie workflow
(according to documentation: every join-node must join all branches of 
corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
am i wrong? / why it's so limited? / is it intentional?

//
//if join-node could just wait until all IN-edges are traversed,
//not necessary from any particular 'corresponding fork-node'
//it would work for all DAGs.
//


  was:
i'd read documentation about Oozie,
it looks interesting, but i've a doubt:

first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
of actions."
so i assumed it can deal with any DAG, but documentation says it is limited to 
specific subset of DAGs, 
ie:  (DAG in ASCII art, directed top-down:)
1
   / \
  2   \
 / \   \
3   4   5
 \   \ /
  \   6
   \ /
7
can't be expressed in Oozie workflow
(according to documentation: every join-node must join all branches of 
corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
am i wrong? / why it's so limited? / is it intentional?

//
//if join-node could just wait until all IN-edges are traversed,
//not necessary from any particular 'corresponding fork-node'
//it would work for all DAGs.
//



> all DAG workflow
> 
>
> Key: OOZIE-2101
> URL: https://issues.apache.org/jira/browse/OOZIE-2101
> Project: Oozie
>  Issue Type: Wish
>Reporter: Grzegorz Chilkiewicz
>Priority: Minor
>
> i'd read documentation about Oozie,
> it looks interesting, but i've a doubt:
> first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
> of actions."
> so i assumed it can deal with any DAG, but documentation says it is limited 
> to specific subset of DAGs, 
> ie:  (DAG in ASCII art, directed top-down:)
> 1
> .../.\
> ..2...\
> ./.\...\
> 3...4...5
> .\...\./
> ..\...6
> ...\./
> 7
> can't be expressed in Oozie workflow
> (according to documentation: every join-node must join all branches of 
> corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
> am i wrong? / why it's so limited? / is it intentional?
> //
> //if join-node could just wait until all IN-edges are traversed,
> //not necessary from any particular 'corresponding fork-node'
> //it would work for all DAGs.
> //



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

[jira] [Created] (OOZIE-2101) all DAG workflow

[Grzegorz Chilkiewicz (JIRA)]

Grzegorz Chilkiewicz created OOZIE-2101:
---

 Summary: all DAG workflow
 Key: OOZIE-2101
 URL: https://issues.apache.org/jira/browse/OOZIE-2101
 Project: Oozie
  Issue Type: Wish
Reporter: Grzegorz Chilkiewicz
Priority: Minor


i'd read documentation about Oozie,
it looks interesting, but i've a doubt:

first web-page says "Oozie Workflow jobs are Directed Acyclical Graphs (DAGs) 
of actions."
so i assumed it can deal with any DAG, but documentation says it is limited to 
specific subset of DAGs, 
ie:  (DAG in ASCII art, directed top-down:)
1
   / \
  2   \
 / \   \
3   4   5
 \   \ /
  \   6
   \ /
7
can't be expressed in Oozie workflow
(according to documentation: every join-node must join all branches of 
corresponding fork-node, so my ASCII DAG isn't valid Oozie workflow...)
am i wrong? / why it's so limited? / is it intentional?

//
//if join-node could just wait until all IN-edges are traversed,
//not necessary from any particular 'corresponding fork-node'
//it would work for all DAGs.
//




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