date:20151116

[jira] [Commented] (OOZIE-2293) Oozie 4.0.1 build failed while building Catalog

2015-11-16 Thread Azrael Seoeun (JIRA)


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

Azrael Seoeun commented on OOZIE-2293:
--

Please backport OOZIE-2293 to branch-4.2. We can not build the latest stable 
version (4.2).

> Oozie 4.0.1 build failed while building Catalog
> ---
>
> Key: OOZIE-2293
> URL: https://issues.apache.org/jira/browse/OOZIE-2293
> Project: Oozie
>  Issue Type: Bug
>Reporter: Janarthanan
>Assignee: Ravi Prakash
>Priority: Critical
> Fix For: trunk
>
> Attachments: OOZIE-2293.01.patch, OOZIE-2293.02.patch
>
>
> Building oozie 4.0.1 with maven failed in Catalog build. Please let me know 
> how to resolve this. 
> Is HCatalog required to be installed prior to oozie. 
> Downloading: http://repository.codehaus.org/asm/asm/maven-metadata.xml
> [WARNING] Could not transfer metadata asm:asm/maven-metadata.xml from/to 
> Codehaus repository (http://repository.codehaus.org/): Failed to transfer 
> file: http://repository.codehaus.org/asm/asm/maven-metadata.xml. Return code 
> is: 410 , ReasonPhrase:Gone.
> [WARNING] Could not transfer metadata asm:asm/maven-metadata.xml from/to 
> local.repository (file:../../local.repository/trunk): Cannot access 
> file:../../local.repository/trunk with type legacy using the available 
> connector factories: BasicRepositoryConnectorFactory
> Downloading: 
> http://repository.codehaus.org/javax/jdo/jdo2-api/2.3-ec/jdo2-api-2.3-ec.pom
> [WARNING] Failure to transfer asm:asm/maven-metadata.xml from 
> http://repository.codehaus.org/ was cached in the local repository, 
> resolution will not be reattempted until the update interval of Codehaus 
> repository has elapsed or updates are forced. Original error: Could not 
> transfer metadata asm:asm/maven-metadata.xml from/to Codehaus repository 
> (http://repository.codehaus.org/): Failed to transfer file: 
> http://repository.codehaus.org/asm/asm/maven-metadata.xml. Return code is: 
> 410 , ReasonPhrase:Gone.
> [WARNING] Failure to transfer asm:asm/maven-metadata.xml from 
> file:../../local.repository/trunk was cached in the local repository, 
> resolution will not be reattempted until the update interval of 
> local.repository has elapsed or updates are forced. Original error: Could not 
> transfer metadata asm:asm/maven-metadata.xml from/to local.repository 
> (file:../../local.repository/trunk): Cannot access 
> file:../../local.repository/trunk with type legacy using the available 
> connector factories: BasicRepositoryConnectorFactory
> [INFO] 
> 
> [INFO] Reactor Summary:
> [INFO] 
> [INFO] Apache Oozie Main .. SUCCESS [  6.031 
> s]
> [INFO] Apache Oozie Client  SUCCESS [  7.637 
> s]
> [INFO] Apache Oozie Hadoop 1.1.1.oozie-4.0.1 .. SUCCESS [  1.004 
> s]
> [INFO] Apache Oozie Hadoop Distcp 1.1.1.oozie-4.0.1 ... SUCCESS [  0.749 
> s]
> [INFO] Apache Oozie Hadoop 1.1.1.oozie-4.0.1 Test . SUCCESS [  0.975 
> s]
> [INFO] Apache Oozie Hadoop 2.3.0.oozie-4.0.1 .. SUCCESS [  1.855 
> s]
> [INFO] Apache Oozie Hadoop 2.3.0.oozie-4.0.1 Test . SUCCESS [  1.206 
> s]
> [INFO] Apache Oozie Hadoop Distcp 2.3.0.oozie-4.0.1 ... SUCCESS [  0.416 
> s]
> [INFO] Apache Oozie Hadoop 0.23.5.oozie-4.0.1 . SUCCESS [  1.594 
> s]
> [INFO] Apache Oozie Hadoop 0.23.5.oozie-4.0.1 Test  SUCCESS [  1.134 
> s]
> [INFO] Apache Oozie Hadoop Distcp 0.23.5.oozie-4.0.1 .. SUCCESS [  0.375 
> s]
> [INFO] Apache Oozie Hadoop Libs ... SUCCESS [  0.061 
> s]
> [INFO] Apache Oozie Hbase 0.94.2.oozie-4.0.1 .. SUCCESS [  0.423 
> s]
> [INFO] Apache Oozie Hbase Libs  SUCCESS [  0.058 
> s]
> [INFO] Apache Oozie HCatalog 0.5.0.oozie-4.0.1  FAILURE [  2.587 
> s]
> [INFO] Apache Oozie HCatalog 0.6.0.oozie-4.0.1  SKIPPED



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

[jira] [Commented] (OOZIE-2397) LAST_ONLY and NONE don't properly handle READY actions

2015-11-16 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-2397:
--

test-patch test run is unfortunately still broken.  The lines that are too long 
are due to SQL changes or docs changes.

> LAST_ONLY and NONE don't properly handle READY actions
> --
>
> Key: OOZIE-2397
> URL: https://issues.apache.org/jira/browse/OOZIE-2397
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 4.2.0
>Reporter: Robert Kanter
>Assignee: Robert Kanter
>Priority: Critical
> Fix For: trunk
>
> Attachments: OOZIE-2397.001.patch
>
>
> When using LAST_ONLY or NONE, actions are supposed to be able to transition 
> from READY to SKIPPED if the right criteria are met, but they don't. This is 
> in contrast to the timeout feature, which does not.
> Here's a more detailed technical description of the problem:
> We handle LAST_ONLY in 
> [CoordMaterializeTransitionXCommand|http://github.mtv.cloudera.com/CDH/oozie/blob/cdh5-4.1.0_5.5.0/core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java#L242]
>  and 
> [CoordActionInputCheckXCommand|http://github.mtv.cloudera.com/CDH/oozie/blob/cdh5-4.1.0_5.5.0/core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java#L156].
>   The former deals with materializing the actions and the behavior to set 
> "old" actions to SKIPPED when materializing them.  The latter deals with 
> checking the input datasets for actions and the behavior to determine if a 
> WAITING action is ready to transition to READY (deps are met) and all that 
> entails, including changing status to READY and queuing a 
> CoordActionReadyXCommand.  If the deps are not met and the dataset is not 
> there yet, it will queue itself at some delay.  So, these only handle the 
> materialization and WAITING states.  However, LAST_ONLY is supposed to also 
> do READY --> SKIPPED if it's condition is met (unlike TIMEDOUT, which can 
> only come from WAITING; *this additional difference should probably be called 
> out in the docs*).  
> [CoordActionReadyXCommand|http://github.mtv.cloudera.com/CDH/oozie/blob/cdh5-4.1.0_5.5.0/core/src/main/java/org/apache/oozie/command/coord/CoordActionReadyXCommand.java#L103]
>  needs to be updated to handle LAST_ONLY.  It currently treats LAST_ONLY the 
> same as LIFO (via CoordJobGetReadyActionsJPAExecutor), where the order is the 
> only difference from FIFO.  After retrieving all READY actions, it should 
> check if any meet their LAST_ONLY condition, and if so, queue a 
> CoordActionSkipXCommand for them (maybe make a bulk version?) instead of a 
> CoordActionStartXCommand.
> We have the same issue with NONE, which has similar behavior.



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

[jira] [Created] (OOZIE-2401) Typo in twiki docs

2015-11-16 Thread Anthony Rojas (JIRA)

Anthony Rojas created OOZIE-2401:


 Summary: Typo in twiki docs
 Key: OOZIE-2401
 URL: https://issues.apache.org/jira/browse/OOZIE-2401
 Project: Oozie
  Issue Type: Bug
  Components: docs
Reporter: Anthony Rojas
Priority: Trivial


There's a minor typo in the twiki documentation that references an anchor  
{{#FilesAchives}} instead of {{#FilesArchives}}

For example, see:
https://oozie.apache.org/docs/4.2.0/DG_ShellActionExtension.html




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

[jira] [Updated] (OOZIE-2401) Typo in twiki docs

2015-11-16 Thread Anthony Rojas (JIRA)


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

Anthony Rojas updated OOZIE-2401:
-
Attachment: OOZIE-2401.001.patch

> Typo in twiki docs
> --
>
> Key: OOZIE-2401
> URL: https://issues.apache.org/jira/browse/OOZIE-2401
> Project: Oozie
>  Issue Type: Bug
>  Components: docs
>Reporter: Anthony Rojas
>Priority: Trivial
> Attachments: OOZIE-2401.001.patch
>
>
> There's a minor typo in the twiki documentation that references an anchor  
> {{#FilesAchives}} instead of {{#FilesArchives}}
> For example, see:
> https://oozie.apache.org/docs/4.2.0/DG_ShellActionExtension.html



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

Re: Review Request 40157: OOZIE-2397: LAST_ONLY and NONE don't properly handle READY actions

2015-11-16 Thread Purshotam Shah


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



core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java (line 
778)


I remember this doesn't work well with diffrent timezone.
You might need to compute it from start date

Like from CoordMaterializeTransitionXCommand.java
.
int intFrequency = Integer.parseInt(coordJob.getFrequency());
effStart = (Calendar) origStart.clone();
effStart.add(freqTU.getCalendarUnit(), actionNumber + 1 * intFrequency);
.


- Purshotam Shah


On Nov. 10, 2015, 10:36 p.m., Robert Kanter wrote:
> 
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/40157/
> ---
> 
> (Updated Nov. 10, 2015, 10:36 p.m.)
> 
> 
> Review request for oozie.
> 
> 
> Bugs: OOZIE-2397
> https://issues.apache.org/jira/browse/OOZIE-2397
> 
> 
> Repository: oozie-git
> 
> 
> Description
> ---
> 
> https://issues.apache.org/jira/browse/OOZIE-2397
> 
> 
> Diffs
> -
> 
>   core/src/main/java/org/apache/oozie/CoordinatorJobBean.java 3ec2eaf 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionInputCheckXCommand.java
>  179dfbf 
>   
> core/src/main/java/org/apache/oozie/command/coord/CoordActionReadyXCommand.java
>  ad9cb12 
>   core/src/main/java/org/apache/oozie/command/coord/CoordCommandUtils.java 
> 131368a 
>   
> core/src/main/java/org/apache/oozie/executor/jpa/CoordJobGetReadyActionsJPAExecutor.java
>  af81091 
>   core/src/main/java/org/apache/oozie/executor/jpa/CoordJobQueryExecutor.java 
> 45d2fc9 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionInputCheckXCommand.java
>  f78dafd 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordActionReadyXCommand.java
>  PRE-CREATION 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordCommandUtils.java 
> 652d792 
>   
> core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
>  77f5518 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobGetReadyActionsJPAExecutor.java
>  c666b87 
>   
> core/src/test/java/org/apache/oozie/executor/jpa/TestCoordJobQueryExecutor.java
>  ee7ad6a 
>   core/src/test/java/org/apache/oozie/test/XDataTestCase.java e6a7d9c 
>   docs/src/site/twiki/CoordinatorFunctionalSpec.twiki faff37f 
> 
> Diff: https://reviews.apache.org/r/40157/diff/
> 
> 
> Testing
> ---
> 
> - Ran relevant unit tests
> - Verified in a cluster that it now has the correct behavior.  I had a 
> Coordinator with a concurrency of 1 and Coord Actions that took  longer than 
> the frequency.  This way, we'd have READY actions that should transition to 
> SKIPPED once the RUNNING action finished.
> 
> 
> Thanks,
> 
> Robert Kanter
> 
>

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

2015-11-16 Thread Apache Jenkins Server

See 

--
[...truncated 8435 lines...]
[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) @ oozie-distro ---
[INFO] Building jar: 

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

[jira] Subscription: Oozie Patch Available

2015-11-16 Thread jira

Issue Subscription
Filter: Oozie Patch Available (58 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-2401  Typo in twiki docs
https://issues.apache.org/jira/browse/OOZIE-2401
OOZIE-2400  Workflow xml configuration parser cannot deal with namespace prefix
https://issues.apache.org/jira/browse/OOZIE-2400
OOZIE-2397  LAST_ONLY and NONE don't properly handle READY actions
https://issues.apache.org/jira/browse/OOZIE-2397
OOZIE-2390  Rerun with failed option removing completed output data
https://issues.apache.org/jira/browse/OOZIE-2390
OOZIE-2380  Oozie Hive action failed with wrong tmp path
https://issues.apache.org/jira/browse/OOZIE-2380
OOZIE-2362  SQL injection in BulkJPAExecutor
https://issues.apache.org/jira/browse/OOZIE-2362
OOZIE-2357  CoordRerun should queue CoordPushDependencyCheckXCommand if there 
is push dependencies
https://issues.apache.org/jira/browse/OOZIE-2357
OOZIE-2349  Method getCoordJobInfo(String jobId, String filter, int offset, int 
length, boolean desc) is not present in LocalOozieClientCoord
https://issues.apache.org/jira/browse/OOZIE-2349
OOZIE-2348  Recovery service keeps on recovering coord action of suspended jobs
https://issues.apache.org/jira/browse/OOZIE-2348
OOZIE-2338  Invalid configuration defined reported for some valid configs
https://issues.apache.org/jira/browse/OOZIE-2338
OOZIE-2312  oozie doesn't purge audit and error log
https://issues.apache.org/jira/browse/OOZIE-2312
OOZIE-2273  MiniOozie does not work outside of Oozie
https://issues.apache.org/jira/browse/OOZIE-2273
OOZIE-2259  Create a callback action 
https://issues.apache.org/jira/browse/OOZIE-2259
OOZIE-2258  Introducing a new counter in the instrumentation log to distinguish 
between the reasons for launcher failure
https://issues.apache.org/jira/browse/OOZIE-2258
OOZIE-2253  Spark Job is failing when it is running in standalone server
https://issues.apache.org/jira/browse/OOZIE-2253
OOZIE-2244  Oozie should mask passwords in the logs when logging command 
arguments
https://issues.apache.org/jira/browse/OOZIE-2244
OOZIE-2243  Kill Command does not kill the child job for java action
https://issues.apache.org/jira/browse/OOZIE-2243
OOZIE-  Oozie UI parent job should be clickable
https://issues.apache.org/jira/browse/OOZIE-
OOZIE-2203  Fix the login example
https://issues.apache.org/jira/browse/OOZIE-2203
OOZIE-2196  Create Local Client for Bundle
https://issues.apache.org/jira/browse/OOZIE-2196
OOZIE-2168  Oozie flow and action names have 50 char limit 
https://issues.apache.org/jira/browse/OOZIE-2168
OOZIE-2134  Remove references to Services.get().getConf() in code
https://issues.apache.org/jira/browse/OOZIE-2134
OOZIE-2106  Make tomcat download url configurable in the pom file
https://issues.apache.org/jira/browse/OOZIE-2106
OOZIE-2105  Make version of submodules configurable with parent version 
https://issues.apache.org/jira/browse/OOZIE-2105
OOZIE-2099  Add test-patch support for patches generated without --no-prefix
https://issues.apache.org/jira/browse/OOZIE-2099
OOZIE-2081  WorkflowJob notification to include coordinator action id 
https://issues.apache.org/jira/browse/OOZIE-2081
OOZIE-2060  Incorrect documentation of Java action config XML filename
https://issues.apache.org/jira/browse/OOZIE-2060
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-2020  Rerun all Failed/killed/timedout coordinator actions rather than 
specifying action numbers
https://issues.apache.org/jira/browse/OOZIE-2020
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

[jira] [Commented] (OOZIE-2293) Oozie 4.0.1 build failed while building Catalog

[jira] [Commented] (OOZIE-2397) LAST_ONLY and NONE don't properly handle READY actions

[jira] [Created] (OOZIE-2401) Typo in twiki docs

[jira] [Updated] (OOZIE-2401) Typo in twiki docs

Re: Review Request 40157: OOZIE-2397: LAST_ONLY and NONE don't properly handle READY actions

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

[jira] Subscription: Oozie Patch Available

7 matches

Site Navigation

Mail list logo

Footer information