date:20180207

[jira] Subscription: Oozie Patch Available

2018-02-07 Thread jira

Issue Subscription
Filter: Oozie Patch Available (111 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3129  Fix test TestConfigurationService.testOozieConfig
https://issues-test.apache.org/jira/browse/OOZIE-3129
OOZIE-3127  Remove redundant check for user
https://issues-test.apache.org/jira/browse/OOZIE-3127
OOZIE-3126  Add option to allow list of users to access system config
https://issues-test.apache.org/jira/browse/OOZIE-3126
OOZIE-3121  bump all maven plugins to latest versions
https://issues-test.apache.org/jira/browse/OOZIE-3121
OOZIE-3118  fix for error: self-closing element not allowed
https://issues-test.apache.org/jira/browse/OOZIE-3118
OOZIE-3117  fix for warning: no @throws for
https://issues-test.apache.org/jira/browse/OOZIE-3117
OOZIE-3116  fix for warning: no description for @throws
https://issues-test.apache.org/jira/browse/OOZIE-3116
OOZIE-3115  fix for javadoc warning: empty  tag
https://issues-test.apache.org/jira/browse/OOZIE-3115
OOZIE-3113  Retry for ZK lock release
https://issues-test.apache.org/jira/browse/OOZIE-3113
OOZIE-3112  SparkConfigrationService overwrites properties provided via 
--properties-file option in SparkAction
https://issues-test.apache.org/jira/browse/OOZIE-3112
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues-test.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues-test.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues-test.apache.org/jira/browse/OOZIE-3091
OOZIE-3083  Make improved version Info backward compatible
https://issues-test.apache.org/jira/browse/OOZIE-3083
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues-test.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues-test.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues-test.apache.org/jira/browse/OOZIE-3062
OOZIE-3002  address findbugs errors in client lib
https://issues-test.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues-test.apache.org/jira/browse/OOZIE-2975
OOZIE-2973  Make sure Oozie works with Hadoop 3 
https://issues-test.apache.org/jira/browse/OOZIE-2973
OOZIE-2969  Drop support for Java 1.7
https://issues-test.apache.org/jira/browse/OOZIE-2969
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues-test.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues-test.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues-test.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues-test.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues-test.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues-test.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues-test.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues-test.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues-test.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues-test.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues-test.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues-test.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues-test.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues-test.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful

[jira] Subscription: Oozie Patch Available

2018-02-07 Thread jira

Issue Subscription
Filter: Oozie Patch Available (104 issues)

Subscriber: ooziedaily

Key Summary
OOZIE-3173  Coordinator job with frequency using cron syntax creates only one 
action in catchup mode
https://issues.apache.org/jira/browse/OOZIE-3173
OOZIE-3172  Upgrade non-transitive Jackson dependencies from 
org.codehaus.jackson to com.fasterxml.jackson
https://issues.apache.org/jira/browse/OOZIE-3172
OOZIE-3135  Configure log4j2 in SqoopMain
https://issues.apache.org/jira/browse/OOZIE-3135
OOZIE-3134  Potential inconsistency between the in-memory SLA map and the Oozie 
database
https://issues.apache.org/jira/browse/OOZIE-3134
OOZIE-3121  bump all maven plugins to latest versions
https://issues.apache.org/jira/browse/OOZIE-3121
OOZIE-3105  testJMXInstrumentation from the 
org.apache.oozie.util.TestMetricsInstrumentation class is flaky
https://issues.apache.org/jira/browse/OOZIE-3105
OOZIE-3094  fix for grammar mistake
https://issues.apache.org/jira/browse/OOZIE-3094
OOZIE-3091  Oozie Sqoop Avro Import fails with "java.lang.NoClassDefFoundError: 
org/apache/avro/mapred/AvroWrapper"
https://issues.apache.org/jira/browse/OOZIE-3091
OOZIE-3071  Oozie 4.3 Spark sharelib ueses a different version of commons-lang3 
than Spark 2.2.0
https://issues.apache.org/jira/browse/OOZIE-3071
OOZIE-3063  Sanitizing variables that are part of openjpa.ConnectionProperties
https://issues.apache.org/jira/browse/OOZIE-3063
OOZIE-3062  Set HADOOP_CONF_DIR for spark action
https://issues.apache.org/jira/browse/OOZIE-3062
OOZIE-3061  Kill only those child jobs which are not already killed
https://issues.apache.org/jira/browse/OOZIE-3061
OOZIE-3002  address findbugs errors in client lib
https://issues.apache.org/jira/browse/OOZIE-3002
OOZIE-2975  code clean up in pig sharelib, replace Exception with more 
explicit, add try with resources, StringBuilder instead of StringBuffer
https://issues.apache.org/jira/browse/OOZIE-2975
OOZIE-2957  Documentation states that starting a coordinator is possible
https://issues.apache.org/jira/browse/OOZIE-2957
OOZIE-2956  Fix Findbugs warnings related to reliance on default encoding in 
oozie-core
https://issues.apache.org/jira/browse/OOZIE-2956
OOZIE-2955  Fix Findbugs warnings related to reliance on default encoding in 
oozie-client
https://issues.apache.org/jira/browse/OOZIE-2955
OOZIE-2954  Fix Checkstyle issues in oozie-client
https://issues.apache.org/jira/browse/OOZIE-2954
OOZIE-2953  Fix Checkstyle issues in oozie-tools
https://issues.apache.org/jira/browse/OOZIE-2953
OOZIE-2952  Fix Findbugs warnings in oozie-sharelib-oozie
https://issues.apache.org/jira/browse/OOZIE-2952
OOZIE-2949  Escape quotes whitespaces in Sqoop  field
https://issues.apache.org/jira/browse/OOZIE-2949
OOZIE-2942  Fix Findbugs warnings in oozie-examples
https://issues.apache.org/jira/browse/OOZIE-2942
OOZIE-2937  Remove redundant groupId from the child pom's
https://issues.apache.org/jira/browse/OOZIE-2937
OOZIE-2934  Fix "Exceptional return value of java.io.File.mkdirs() ignored" 
Findbugs error in oozie-sharelib-spark
https://issues.apache.org/jira/browse/OOZIE-2934
OOZIE-2927  Append new line character for Hive2 query using query tag
https://issues.apache.org/jira/browse/OOZIE-2927
OOZIE-2914  Consolidate Trim 
https://issues.apache.org/jira/browse/OOZIE-2914
OOZIE-2883  OOZIE throw the error "Missing 
[oozie.service.ProxyUserService.proxyuser.oozie.service.ProxyUserService.proxyuser.mr.groups]
 property"
https://issues.apache.org/jira/browse/OOZIE-2883
OOZIE-2877  Oozie Git Action
https://issues.apache.org/jira/browse/OOZIE-2877
OOZIE-2867  Timezone handling for Coordinators: emphasize "Continent/City" 
format
https://issues.apache.org/jira/browse/OOZIE-2867
OOZIE-2834  ParameterVerifier logging non-useful warning for workflow definition
https://issues.apache.org/jira/browse/OOZIE-2834
OOZIE-2833  when using uber mode the regex pattern used in the 
extractHeapSizeMB method does not allow heap sizes specified in bytes.
https://issues.apache.org/jira/browse/OOZIE-2833
OOZIE-2829  Improve sharelib upload to accept multiple source folders
https://issues.apache.org/jira/browse/OOZIE-2829
OOZIE-2826  Falcon feed fails to aws s3; Oozie joda time version does not meet 
required jar version 2.2 or later
https://issues.apache.org/jira/browse/OOZIE-2826
OOZIE-2814  OYA: Update example workflows to newest schemas
https://issues.apache.org/jira/browse/OOZIE-2814
OOZIE-2812  SparkConfigurationService should support loading configurations 
from multiple Spark versions
https://issues.apache.org/jira/browse/OOZIE

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-07 Thread Rohini Palaniswamy

+1 (binding)

- Verified md5, signature, release log and rat report
- Ran all the unit tests and they are good.
- Created distro with bin/mkdistro.sh -DskipTests -Puber -Phadoop-2
- Checked the UI and executed a simple workflow
- Verified that the tomcat is now 6.0.53

Looks like the vote ends on Feb 12 which is 7 days and is very long. Isn't
it usually 72 hours excluding weekends and holidays?

Regards,
Rohini

On Wed, Feb 7, 2018 at 1:35 PM, Robert Kanter  wrote:

> Here's what I did:
> - Verified md5
> - Verified signature (gpg)
> - Looked at rat report
> - Looked at release log
> - Verified Tomcat is version 6.0.53
> - Built Oozie against Hadoop 2.7.2, using an empty local maven repo
> - Ran a few of the examples, clicked around the UI, tried various CLI
> commands, looked at the REST output, launcher log output, etc
>
>
> +1
>
> On Tue, Feb 6, 2018 at 7:24 PM, Artem Ervits 
> wrote:
>
> > Attila, AFAIK, these properties are in my core-site.xml except for last
> > one, mapreduce.framework.name is in mapred-site.xml. I'll have to double
> > check on the proxyuser.root.hosts as I believe my service runs with user
> > oozie not root and get back to you.
> >
> > On Tue, Feb 6, 2018 at 3:49 PM, Attila Sasvari 
> > wrote:
> >
> > > +1 (binding)
> > >
> > > - Verified MD5 hash, signature, rat_report, release log are OK
> > > - Built Oozie against Hadoop 2.7.5 (did not build against other Hadoop
> > > versions this time)
> > > - Installed Oozie sharelib
> > > - Some example workflows I submitted to a 1-node Hadoop 2.7.5 (running
> in
> > > pseudo distributed mode for tests) succeeded: ( aggregator bundle
> > > coord-input-logic cron cron-schedule custom-main datelist-java-main
> demo
> > > distcp hadoop-el hcatalog java-main map-reduce no-op pig shell sla
> sqoop
> > > sqoop-freeform ssh streaming subwf )
> > > - Verified basic functionality of the Web UI (version, Job DAG, Job
> logs)
> > >
> > >
> > > Artem, have you specified conf/hadoop-conf/core-site.xml with all the
> > > details Oozie needs to communicate with a Hadoop cluster?
> > >
> > > In my local environment, I use a pseudo Hadoop 2.7.5. My
> > > conf/hadoop-conf/core-site.xml is as follows:
> > > 
> > > 
> > > 
> > > 
> > > 
> > >   
> > > fs.defaultFS
> > > hdfs://localhost:9000
> > >   
> > >   
> > > hadoop.proxyuser.root.hosts
> > > *
> > >   
> > >   
> > > hadoop.proxyuser.root.groups
> > > *
> > >   
> > > 
> > > mapreduce.framework.name
> > > yarn
> > > 
> > > 
> > >
> > >
> > > On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits 
> > > wrote:
> > >
> > > > jdk: 1.8.0_161
> > > > hadoop: 2.7.5
> > > > md5: OK
> > > > curl http://localhost:11000/oozie/v1/admin/status
> > > > {"systemMode":"NORMAL"}
> > > >
> > > > curl http://localhost:11000/oozie/v2/admin/status
> > > > {"systemMode":"NORMAL"}
> > > >
> > > >
> > > > I also got in oozie-ops.log
> > > >
> > > >   STARTUP MSG: Oozie BUILD_VERSION [4.3.1] compiled by [oozie] on
> > > > [2018.02.06-16:30:43GMT]
> > > >   STARTUP MSG:   revision [unavailable]@[unavailable]
> > > >
> > > > so perhaps we may want to add but not critical OOZIE-2004,
> OOZIE-3083,
> > > > OOZIE-3152.
> > > >
> > > >  submitted a job and got but that is most likely my environment.
> > > Otherwise
> > > > +1
> > > >
> > > > 2018-02-06 18:09:37,635  WARN ActionStartXCommand:523 - SERVER[
> > > > hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
> > > > JOB[000-180206180622504-oozie-oozi-W]
> > > > ACTION[000-180206180622504-oozie-oozi-W@python-node] Error
> > starting
> > > > action [python-node]. ErrorType [ERROR], ErrorCode
> > > > [UnsupportedOperationException], Message [
> > UnsupportedOperationException:
> > > > Accessing local file system is not allowed]
> > > > org.apache.oozie.action.ActionExecutorException:
> > > > UnsupportedOperationException: Accessing local file system is not
> > allowed
> > > > at
> > > > org.apache.oozie.action.ActionExecutor.convertException(Acti
> > > > onExecutor.java:446)
> > > > at
> > > > org.apache.oozie.action.hadoop.JavaActionExecutor.submitLaun
> > > > cher(JavaActionExecutor.java:1204)
> > > > at
> > > > org.apache.oozie.action.hadoop.JavaActionExecutor.start(Java
> > > > ActionExecutor.java:1386)
> > > > at
> > > > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > > > onStartXCommand.java:234)
> > > > at
> > > > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > > > onStartXCommand.java:65)
> > > > at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> > > > at
> > > > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > > > ble.call(CallableQueueService.java:332)
> > > > at
> > > > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > > > ble.call(CallableQueueService.java:261)
> > > > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > > at
> > > > org.apache.oozie.service.CallableQueueService$CallableWrappe
> > > > r.run(CallableQ

[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config

2018-02-07 Thread JIRA


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

Hervé Boutemy commented on OOZIE-3163:
--

I'm glad you like it: as a Maven PMC member, previous rendering just made me 
not feel proud of Maven itself :)

> Improve documentation rendering: use fluido skin and better config
> --
>
> Key: OOZIE-3163
> URL: https://issues.apache.org/jira/browse/OOZIE-3163
> Project: Oozie
>  Issue Type: Task
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: 34.patch, oozie-docs-coordinator-fs-fluido.png, 
> oozie-docs-coordinator-fs-old.png, oozie-docs-index-fluido.png, 
> oozie-docs-index-old.png
>
>
> Current output is really ugly: as Maven maintainer, I can't let Oozie with 
> such awful result :)
> Even with old maven-site-plugin 2.0-beta-6 (we'll see later how to upgrade), 
> using Fluido skin would improve output a lot
> Pull Request coming



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

2018-02-07 Thread Robert Kanter

Here's what I did:
- Verified md5
- Verified signature (gpg)
- Looked at rat report
- Looked at release log
- Verified Tomcat is version 6.0.53
- Built Oozie against Hadoop 2.7.2, using an empty local maven repo
- Ran a few of the examples, clicked around the UI, tried various CLI
commands, looked at the REST output, launcher log output, etc


+1

On Tue, Feb 6, 2018 at 7:24 PM, Artem Ervits  wrote:

> Attila, AFAIK, these properties are in my core-site.xml except for last
> one, mapreduce.framework.name is in mapred-site.xml. I'll have to double
> check on the proxyuser.root.hosts as I believe my service runs with user
> oozie not root and get back to you.
>
> On Tue, Feb 6, 2018 at 3:49 PM, Attila Sasvari 
> wrote:
>
> > +1 (binding)
> >
> > - Verified MD5 hash, signature, rat_report, release log are OK
> > - Built Oozie against Hadoop 2.7.5 (did not build against other Hadoop
> > versions this time)
> > - Installed Oozie sharelib
> > - Some example workflows I submitted to a 1-node Hadoop 2.7.5 (running in
> > pseudo distributed mode for tests) succeeded: ( aggregator bundle
> > coord-input-logic cron cron-schedule custom-main datelist-java-main demo
> > distcp hadoop-el hcatalog java-main map-reduce no-op pig shell sla sqoop
> > sqoop-freeform ssh streaming subwf )
> > - Verified basic functionality of the Web UI (version, Job DAG, Job logs)
> >
> >
> > Artem, have you specified conf/hadoop-conf/core-site.xml with all the
> > details Oozie needs to communicate with a Hadoop cluster?
> >
> > In my local environment, I use a pseudo Hadoop 2.7.5. My
> > conf/hadoop-conf/core-site.xml is as follows:
> > 
> > 
> > 
> > 
> > 
> >   
> > fs.defaultFS
> > hdfs://localhost:9000
> >   
> >   
> > hadoop.proxyuser.root.hosts
> > *
> >   
> >   
> > hadoop.proxyuser.root.groups
> > *
> >   
> > 
> > mapreduce.framework.name
> > yarn
> > 
> > 
> >
> >
> > On Tue, Feb 6, 2018 at 8:10 PM, Artem Ervits 
> > wrote:
> >
> > > jdk: 1.8.0_161
> > > hadoop: 2.7.5
> > > md5: OK
> > > curl http://localhost:11000/oozie/v1/admin/status
> > > {"systemMode":"NORMAL"}
> > >
> > > curl http://localhost:11000/oozie/v2/admin/status
> > > {"systemMode":"NORMAL"}
> > >
> > >
> > > I also got in oozie-ops.log
> > >
> > >   STARTUP MSG: Oozie BUILD_VERSION [4.3.1] compiled by [oozie] on
> > > [2018.02.06-16:30:43GMT]
> > >   STARTUP MSG:   revision [unavailable]@[unavailable]
> > >
> > > so perhaps we may want to add but not critical OOZIE-2004, OOZIE-3083,
> > > OOZIE-3152.
> > >
> > >  submitted a job and got but that is most likely my environment.
> > Otherwise
> > > +1
> > >
> > > 2018-02-06 18:09:37,635  WARN ActionStartXCommand:523 - SERVER[
> > > hadoop.example.com] USER[vagrant] GROUP[-] TOKEN[] APP[python-wf]
> > > JOB[000-180206180622504-oozie-oozi-W]
> > > ACTION[000-180206180622504-oozie-oozi-W@python-node] Error
> starting
> > > action [python-node]. ErrorType [ERROR], ErrorCode
> > > [UnsupportedOperationException], Message [
> UnsupportedOperationException:
> > > Accessing local file system is not allowed]
> > > org.apache.oozie.action.ActionExecutorException:
> > > UnsupportedOperationException: Accessing local file system is not
> allowed
> > > at
> > > org.apache.oozie.action.ActionExecutor.convertException(Acti
> > > onExecutor.java:446)
> > > at
> > > org.apache.oozie.action.hadoop.JavaActionExecutor.submitLaun
> > > cher(JavaActionExecutor.java:1204)
> > > at
> > > org.apache.oozie.action.hadoop.JavaActionExecutor.start(Java
> > > ActionExecutor.java:1386)
> > > at
> > > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > > onStartXCommand.java:234)
> > > at
> > > org.apache.oozie.command.wf.ActionStartXCommand.execute(Acti
> > > onStartXCommand.java:65)
> > > at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> > > at
> > > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > > ble.call(CallableQueueService.java:332)
> > > at
> > > org.apache.oozie.service.CallableQueueService$CompositeCalla
> > > ble.call(CallableQueueService.java:261)
> > > at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> > > at
> > > org.apache.oozie.service.CallableQueueService$CallableWrappe
> > > r.run(CallableQueueService.java:179)
> > > at
> > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPool
> > > Executor.java:1149)
> > > at
> > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoo
> > > lExecutor.java:624)
> > > at java.lang.Thread.run(Thread.java:748)
> > > Caused by: java.lang.UnsupportedOperationException: Accessing local
> file
> > > system is not allowed
> > > at
> > > org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalF
> > > ileSystem.java:48)
> > > at org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSys
> > > tem.java:47)
> > > at org.apache.hadoop.fs.FileSystem.createFileSystem(
> > FileSystem.java:2667)
> > > at org.apache.hadoop.fs.FileSystem.access$200(FileSystem.java:93)
> > > at o

[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config

2018-02-07 Thread Robert Kanter (JIRA)


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

Robert Kanter commented on OOZIE-3163:
--

Wow!  That looks so much better.  Thanks for taking care of this.

> Improve documentation rendering: use fluido skin and better config
> --
>
> Key: OOZIE-3163
> URL: https://issues.apache.org/jira/browse/OOZIE-3163
> Project: Oozie
>  Issue Type: Task
>  Components: docs
>Affects Versions: 4.3.0
>Reporter: Hervé Boutemy
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: 34.patch, oozie-docs-coordinator-fs-fluido.png, 
> oozie-docs-coordinator-fs-old.png, oozie-docs-index-fluido.png, 
> oozie-docs-index-old.png
>
>
> Current output is really ugly: as Maven maintainer, I can't let Oozie with 
> such awful result :)
> Even with old maven-site-plugin 2.0-beta-6 (we'll see later how to upgrade), 
> using Fluido skin would improve output a lot
> Pull Request coming



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread Andras Piros (JIRA)


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

Andras Piros commented on OOZIE-3173:
-

Failed tests are not related. [~gezapeti] can you please review? Thanks!

> Coordinator job with frequency using cron syntax creates only one action in 
> catchup mode
> 
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job 
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time 
> lies also in the past), would create only one action, independent of 
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times 
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now, 
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{15}} -> ten actions should be created



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3173:
--


Testing JIRA OOZIE-3173

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 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}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{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{color} There are no new bugs found in total.
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {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/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {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/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {color:green}+1{color} There are no new bugs found in [sharelib/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [core].
. {color:green}+1{color} There are no new bugs found in [tools].
. {color:green}+1{color} There are no new bugs found in [server].
{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: 2092
.Tests failed: 4
.Tests errors: 1

.The patch failed the following testcases:

testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)

.Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

.{color:orange}Tests failed at first run:{color}
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{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}

{color:red}. There is at least one warning, please check{color}

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

. https://builds.apache.org/job/PreCommit-OOZIE-Build/383/



> Coordinator job with frequency using cron syntax creates only one action in 
> catchup mode
> 
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job 
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time 
> lies also in the past), would create only one action, independent of 
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times 
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now, 
> endTime), startTime + frequency * throttle)}}.
> Some exampl

Failed: OOZIE-3173 PreCommit Build #383

2018-02-07 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3173
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/383/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.59 MB...]
[INFO] There are no new bugs found totally].
[TRACE] FindBugs diffs checked and reports created
[TRACE] Summary file size is 2252 bytes
[TRACE] Full summary file size is 1314 bytes
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar]
 removed
[TRACE] File 
[/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/FINDBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5sum]
 removed
  Running test-patch task BACKWARDS_COMPATIBILITY
  Running test-patch task TESTS
  Running test-patch task DISTRO


Testing JIRA OOZIE-3173

Cleaning local git workspace



+1 PATCH_APPLIES
+1 CLEAN
+1 RAW_PATCH_ANALYSIS
+1 the patch does not introduce any @author tags
+1 the patch does not introduce any tabs
+1 the patch does not introduce any trailing spaces
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [tools].
 +1 There are no new bugs found in [server].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2092
Tests failed: 4
Tests errors: 1

The patch failed the following testcases:

testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerService)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)

Tests failing with errors:
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
TestCoordActionsKillXCommand#testActionKillCommandActionNumbers
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/383/

Adding comment to JIRA
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0100  37540 0  100  3754  0   3666  0:00:01  0:00:01 --:--:--  
3669{"self":"https://issues.apache.org/jira/rest/api/2/issue/13136381/comment/16355976","id":"16355976","author":{"self":"https://issues.apache.org/jira/rest/api/2/user?username=hadoopqa","name":"hadoopqa","key":"hadoopqa","emailAddress":"blackhole
 at hadoop dot apache dot 
org","avatarUrls":{"48x48":"https://issues.apache.org/jira/secure/useravatar?ownerId=hadoopqa&avatarId=10393","24x24":"https://issues.apache.org/jira/secure/useravatar?size=small&ownerId=hadoopqa&avatarId=10393","16x16":"https://issues.apache.org/jira/secure/useravatar?size=xsmall&ownerId=hadoopqa&avatarId=10393","32x32":"https://issues.apache.org/jira/secure/useravatar?size=medium&ownerId=hadoopqa&avatarId=10393"},"displayName":"Hadoop
 QA","active":true,"timeZone":"Etc/UTC"},"body":"\nTesting JIRA 
OOZIE-3173\n\nCleaning local git 
workspace\n\n\n\n{color:green}+1 
PATCH_APPLIES{color}\n{color:green}+1 CLEAN{color}\n{color:green}+1 
RAW_PATCH_ANALYSIS{color}\n.

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3173:
--

PreCommit-OOZIE-Build started


> Coordinator job with frequency using cron syntax creates only one action in 
> catchup mode
> 
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job 
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time 
> lies also in the past), would create only one action, independent of 
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times 
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now, 
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{15}} -> ten actions should be created



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3173:
--


Testing JIRA OOZIE-3173

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 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}WARNING{color}: the current HEAD has 100 Javadoc warning(s)
{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{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 [server].
. {color:green}+1{color} There are no new bugs found in [client].
. {color:green}+1{color} There are no new bugs found in [docs].
. {color:green}+1{color} There are no new bugs found in [examples].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive].
. {color:green}+1{color} There are no new bugs found in [sharelib/pig].
. {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/streaming].
. {color:green}+1{color} There are no new bugs found in [sharelib/spark].
. {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/sqoop].
. {color:green}+1{color} There are no new bugs found in [sharelib/hive2].
. {color:green}+1{color} There are no new bugs found in [sharelib/oozie].
. {color:green}+1{color} There are no new bugs found in [webapp].
. {color:green}+1{color} There are no new bugs found in [tools].
{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: 2092
.Tests failed: 17
.Tests errors: 12

.The patch failed the following testcases:

testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

.Tests failing with errors:
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListe

Failed: OOZIE-3173 PreCommit Build #382

2018-02-07 Thread Apache Jenkins Server

Jira: https://issues.apache.org/jira/browse/OOZIE-3173
Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/382/

###
## LAST 100 LINES OF THE CONSOLE 
###
[...truncated 1.61 MB...]
+1 the patch does not introduce any line longer than 132
+1 the patch adds/modifies 1 testcase(s)
+1 RAT
+1 the patch does not seem to introduce new RAT warnings
+1 JAVADOC
+1 the patch does not seem to introduce new Javadoc warnings
WARNING: the current HEAD has 100 Javadoc warning(s)
+1 COMPILE
+1 HEAD compiles
+1 patch compiles
+1 the patch does not seem to introduce new javac warnings
+1 There are no new bugs found in total.
 +1 There are no new bugs found in [core].
 +1 There are no new bugs found in [server].
 +1 There are no new bugs found in [client].
 +1 There are no new bugs found in [docs].
 +1 There are no new bugs found in [examples].
 +1 There are no new bugs found in [sharelib/hive].
 +1 There are no new bugs found in [sharelib/pig].
 +1 There are no new bugs found in [sharelib/distcp].
 +1 There are no new bugs found in [sharelib/streaming].
 +1 There are no new bugs found in [sharelib/spark].
 +1 There are no new bugs found in [sharelib/hcatalog].
 +1 There are no new bugs found in [sharelib/sqoop].
 +1 There are no new bugs found in [sharelib/hive2].
 +1 There are no new bugs found in [sharelib/oozie].
 +1 There are no new bugs found in [webapp].
 +1 There are no new bugs found in [tools].
+1 BACKWARDS_COMPATIBILITY
+1 the patch does not change any JPA Entity/Colum/Basic/Lob/Transient 
annotations
+1 the patch does not modify JPA files
-1 TESTS
Tests run: 2092
Tests failed: 17
Tests errors: 12

The patch failed the following testcases:

testCoordinatorActionSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testCoordinatorActionSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectors(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuspendEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsAnd(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testConnectionDrop(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsNegative(org.apache.oozie.jms.TestJMSJobEventListener)
testWorkflowJobSelectorsOr(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobSuccessEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionWaitingEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobFailureEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnCoordinatorActionStartEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testOnWorkflowJobStartedEvent(org.apache.oozie.jms.TestJMSJobEventListener)
testPartitionDependency(org.apache.oozie.service.TestPartitionDependencyManagerEhcache)
testCoordActionRecoveryServiceForWaitingRegisterPartition(org.apache.oozie.service.TestRecoveryService)

Tests failing with errors:
testDropEventTypeMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testCacheUpdateByMessage(org.apache.oozie.jms.TestHCatMessageHandler)
testThreadLocalSession(org.apache.oozie.jms.TestDefaultConnectionContext)
testConnectionRetry(org.apache.oozie.service.TestJMSAccessorService)
testOnSLADurationMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectorsNegative(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMetEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAStartMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testSLAJobSelectors(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLAEndMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)
testOnSLADurationMissEvent(org.apache.oozie.jms.TestJMSSLAEventListener)

Tests failed at first run:
TestJavaActionExecutor#testCredentialsSkip
For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
+1 DISTRO
+1 distro tarball builds with the patch 


-1 Overall result, please check the reported -1(s)

 There is at least one warning, please check

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

 https://builds.apache.org/job/PreCommit-OOZIE-Build/382/

Adding comment to JIRA
  % 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{"self":"https://issues.apache.org/jira/rest/api/2/issue/13136381/comment/16355845","id":"16355845","author":{"self":"https://issues.apache.org/jira/res

[jira] [Updated] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread Andras Piros (JIRA)


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

Andras Piros updated OOZIE-3173:

Attachment: OOZIE-3173.002.patch

> Coordinator job with frequency using cron syntax creates only one action in 
> catchup mode
> 
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job 
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time 
> lies also in the past), would create only one action, independent of 
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times 
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now, 
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{15}} -> ten actions should be created



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 65535: OOZIE-3173 Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread András Piros via Review Board


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

(Updated Feb. 7, 2018, 4:49 p.m.)


Review request for oozie, Attila Sasvari and Peter Cseh.


Changes
---

Addressing review comments.


Repository: oozie-git


Description
---

OOZIE-3173 Coordinator job with frequency using cron syntax creates only one 
action in catchup mode


Diffs (updated)
-

  
core/src/main/java/org/apache/oozie/command/coord/CoordMaterializeTransitionXCommand.java
 91d3508d128032ea5928cd5c6de482a65008c2bc 
  
core/src/test/java/org/apache/oozie/command/coord/TestCoordMaterializeTransitionXCommand.java
 2a648d7c35c1a396e099ab27ab33d91e95d119d5 


Diff: https://reviews.apache.org/r/65535/diff/2/

Changes: https://reviews.apache.org/r/65535/diff/1-2/


Testing
---

New unit tests:

* 
`TestCoordMaterializeTransitionXCommand#testCronFrequencyCatchupThrottleLessThanDuration()`
* 
`TestCoordMaterializeTransitionXCommand#testCronFrequencyCatchupThrottleEqualsDuration`
* 
`TestCoordMaterializeTransitionXCommand#testCronFrequencyCatchupThrottleMoreThanDuration`


Thanks,

András Piros

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

2018-02-07 Thread Hadoop QA (JIRA)


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

Hadoop QA commented on OOZIE-3173:
--

PreCommit-OOZIE-Build started


> Coordinator job with frequency using cron syntax creates only one action in 
> catchup mode
> 
>
> Key: OOZIE-3173
> URL: https://issues.apache.org/jira/browse/OOZIE-3173
> Project: Oozie
>  Issue Type: Bug
>  Components: coordinator
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3173.001.patch, OOZIE-3173.002.patch
>
>
> Using a coordinator with cron based {{frequency}}, when in catchup mode (job 
> is still in {{PREP}}), {{startTime}} lies in the past, next materialize time 
> lies also in the past), would create only one action, independent of 
> {{throttle}} value.
> As many actions should be created in catchup mode, as many times 
> {{frequency}} would fit in between {{startTime}}, {{Math.min(Math.min(now, 
> endTime), startTime + frequency * throttle)}}.
> Some examples, {{frequency="0 * * * *"}}:
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{1}} -> one action should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{3}} -> three actions should be created
> * when between {{startTime}} and {{endTime}} there are 10 hours, both lie in 
> the past, and {{throttle}} is {{15}} -> ten actions should be created



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: Review Request 64029: OOZIE-2339 Provide an API for writing jobs based on the XSD schemas

2018-02-07 Thread Attila Sasvari via Review Board


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




client/src/main/java/org/apache/oozie/cli/WorkflowFactoryCompiler.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/DistcpAction.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/Hive2ActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/HiveAction.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/HiveActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/JavaAction.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/JavaActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/Launcher.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/LauncherBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/PigAction.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/PigActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/ShellActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/SparkAction.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/SparkActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/SqoopAction.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/SqoopActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/action/SshActionBuilder.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/factory/SimpleWorkflowFactory.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/factory/WorkflowFactory.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/CredentialsConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/DistcpConfigurationConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/DistcpPrepareConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/GlobalConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/Hive2ConfigurationConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/Hive2LauncherConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/Hive2PrepareConverter.java
Lines 1 (patched)


missing license



jobs/jobs-api/src/main/java/org/apache/oozie/jobs/api/mapping/HiveConfigurationConverter.java
Lines 1 (patched)

[jira] [Assigned] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

2018-02-07 Thread Peter Cseh (JIRA)


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

Peter Cseh reassigned OOZIE-3178:
-

Assignee: Peter Cseh

> ./bin/mkdistro.sh -Papache-release fails due to javadoc errors
> --
>
> Key: OOZIE-3178
> URL: https://issues.apache.org/jira/browse/OOZIE-3178
> Project: Oozie
>  Issue Type: Bug
>Affects Versions: 5.0.0
>Reporter: Peter Cseh
>Assignee: Peter Cseh
>Priority: Blocker
>
> The distro creation script fails if it's called using the profile 
> apache-release.
> The first batch of errors are javadoc-related.
> We should fix them and also enhance our pre-commit hook to prevent this from 
> happening in the future.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

2018-02-07 Thread Peter Cseh (JIRA)

Peter Cseh created OOZIE-3178:
-

 Summary: ./bin/mkdistro.sh -Papache-release fails due to javadoc 
errors
 Key: OOZIE-3178
 URL: https://issues.apache.org/jira/browse/OOZIE-3178
 Project: Oozie
  Issue Type: Bug
Affects Versions: 5.0.0
Reporter: Peter Cseh


The distro creation script fails if it's called using the profile 
apache-release.
The first batch of errors are javadoc-related.
We should fix them and also enhance our pre-commit hook to prevent this from 
happening in the future.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Attila Sasvari (JIRA)


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

Attila Sasvari reassigned OOZIE-3176:
-

Assignee: Alisha Prabhu

> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Assignee: Alisha Prabhu
>Priority: Minor
> Attachments: Checkstyle-erros.txt
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> I have attached the Checkstyle-errors.txt file, that has the errors occurred 
> while building.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Attila Sasvari (JIRA)


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

Attila Sasvari commented on OOZIE-3176:
---

[~alishap] many thanks for filing this JIRA, I added you to contributors and 
assigned the ticket too you.

I can confirm {{mvn clean install -DskipTests 
-Dmaven.javadoc.opts="-Xdoclint:none"}} fails on master because of a checkstyle 
error, {{core/target/checkstyle-result.xml}} shows:
{code}

http://www.apache.org/licenses/LICENSE-2.0'."; 
source="com.puppycrawl.tool
s.checkstyle.checks.header.HeaderCheck"/> 
{code}

WorkflowJobsBasicInfoFromParentId was introduced by OOZIE-1401.amend.003.patch. 
On that day, the Oozie PreCommit build failed to add comment (JIRA  was 
updated).

> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Minor
> Attachments: Checkstyle-erros.txt
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> I have attached the Checkstyle-errors.txt file, that has the errors occurred 
> while building.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3177) Unclear ooziedb -sqlFile option behaviour

2018-02-07 Thread Julia Kinga Marton (JIRA)

Julia Kinga Marton created OOZIE-3177:
-

 Summary: Unclear ooziedb -sqlFile option behaviour 
 Key: OOZIE-3177
 URL: https://issues.apache.org/jira/browse/OOZIE-3177
 Project: Oozie
  Issue Type: Bug
  Components: scripts
Reporter: Julia Kinga Marton


There are two scenarios when running ooziedb.sh with -sqlscript option can lead 
to misunderstandings:

full command: ooziedb.sh upgrade -sqlfile oozie-upgrade.sql
 # if there are no changes, the following information is printed out: "The SQL 
commands have been written to: oozie-upgrade.sql", however if there is no SQL 
command, the file will be not created. 
 # If there are changes and the file is created, it is stored in the /tmp/ 
directory. In the log message it would be good to print out the full path to 
the file, not only the file name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Alisha Prabhu (JIRA)


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

Alisha Prabhu updated OOZIE-3176:
-
Environment: 
# uname -a
Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux

  was:
 # uname -a
Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux


> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment: # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Minor
> Attachments: Checkstyle-erros.txt
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> I have attached the Checkstyle-errors.txt file, that has the errors occurred 
> while building.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Alisha Prabhu (JIRA)


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

Alisha Prabhu updated OOZIE-3176:
-
Description: 
There are multiple checkstyle violations in the Oozie-core module.

Maven command used is mvn clean install -DskipTests

I have attached the Checkstyle-errors.txt file, that has the errors occurred 
while building.

  was:
There are multiple checkstyle violations in the Oozie-core module.

Maven command used is mvn clean install -DskipTests

 


> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment:  # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Minor
> Attachments: Checkstyle-erros.txt
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
> I have attached the Checkstyle-errors.txt file, that has the errors occurred 
> while building.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Alisha Prabhu (JIRA)


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

Alisha Prabhu updated OOZIE-3176:
-
Attachment: Checkstyle-erros.txt

> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment:  # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Minor
> Attachments: Checkstyle-erros.txt
>
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3172) Upgrade non-transitive Jackson dependencies from org.codehaus.jackson to com.fasterxml.jackson

2018-02-07 Thread Attila Sasvari (JIRA)


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

Attila Sasvari commented on OOZIE-3172:
---

[~andras.piros] thanks for submitting example workflows. Workflows succeeded, 
so it looks good to me. [~gezapeti] can you answer last question?

(If it breaks Hive workflows, we can file a separate JIRA. It would be nice to 
validate.)

> Upgrade non-transitive Jackson dependencies from org.codehaus.jackson to 
> com.fasterxml.jackson
> --
>
> Key: OOZIE-3172
> URL: https://issues.apache.org/jira/browse/OOZIE-3172
> Project: Oozie
>  Issue Type: Improvement
>  Components: core
>Affects Versions: 5.0.0b1
>Reporter: Andras Piros
>Assignee: Andras Piros
>Priority: Major
> Attachments: OOZIE-3172.001.patch, OOZIE-3172.002.patch
>
>
> Jackson 1.9.3 is way too old, and has several security vulnerabilities as 
> well. Jackson 2.9.2 covers most of these.
> Let's switch from {{org.codehaus.jackson}} to {{com.fasterxml.jackson}} in 
> Oozie's direct (non-transitive) dependencies.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Alisha Prabhu (JIRA)


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

Alisha Prabhu updated OOZIE-3176:
-
Environment: 
 # uname -a
Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux

  was:
~# uname -a
Linux pts00432-vm20 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

 


> Oozie-core fails with checkstyle errors.
> 
>
> Key: OOZIE-3176
> URL: https://issues.apache.org/jira/browse/OOZIE-3176
> Project: Oozie
>  Issue Type: Bug
>  Components: core
>Affects Versions: 5.0.0b1
> Environment:  # uname -a
> Linux in-ibmibm283.persistent.co.in 3.10.0-229.14.1.el7.x86_64 #1 SMP Tue Aug 
> 25 11:21:22 EDT 2015 x86_64 x86_64 x86_64 GNU/Linux
>Reporter: Alisha Prabhu
>Priority: Minor
>
> There are multiple checkstyle violations in the Oozie-core module.
> Maven command used is mvn clean install -DskipTests
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (OOZIE-3176) Oozie-core fails with checkstyle errors.

2018-02-07 Thread Alisha Prabhu (JIRA)

Alisha Prabhu created OOZIE-3176:


 Summary: Oozie-core fails with checkstyle errors.
 Key: OOZIE-3176
 URL: https://issues.apache.org/jira/browse/OOZIE-3176
 Project: Oozie
  Issue Type: Bug
  Components: core
Affects Versions: 5.0.0b1
 Environment: ~# uname -a
Linux pts00432-vm20 3.16.0-30-generic #40~14.04.1-Ubuntu SMP Thu Jan 15 
17:42:36 UTC 2015 ppc64le ppc64le ppc64le GNU/Linux

 
Reporter: Alisha Prabhu


There are multiple checkstyle violations in the Oozie-core module.

Maven command used is mvn clean install -DskipTests

 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (OOZIE-3134) Potential inconsistency between the in-memory SLA map and the Oozie database

2018-02-07 Thread Julia Kinga Marton (JIRA)


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

Julia Kinga Marton commented on OOZIE-3134:
---

Thank you [~rohini] for pointing out the  OOZIE-1980 issue. I will keep that in 
mind and will continue with this small fix for the scenario 2.

> Potential inconsistency between the in-memory SLA map and the Oozie database
> 
>
> Key: OOZIE-3134
> URL: https://issues.apache.org/jira/browse/OOZIE-3134
> Project: Oozie
>  Issue Type: Bug
>Reporter: Attila Sasvari
>Assignee: Julia Kinga Marton
>Priority: Major
> Fix For: 5.0.0
>
> Attachments: OOZIE-3134-001.patch, OOZIE-3134-002.patch
>
>
> Upon {{SLACalculatorMemory.addRegistration}}, Oozie puts an entry into an 
> in-memory concurrent hashmap ("slaMap"), and later [persists 
> it|https://github.com/apache/oozie/blob/50f4b5984832941f1341586e43fd832c293b3275/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L380]
>  in the Oozie database. 
> However, if there is a failure during the database operation, a 
> {{JPAExecutorException}} is thrown, and the entry [is not removed from the 
> SLA map| 
> https://github.com/apache/oozie/blob/50f4b5984832941f1341586e43fd832c293b3275/core/src/main/java/org/apache/oozie/sla/SLACalculatorMemory.java#L393].
> It may introduce inconsistency between the Oozie database and the SLA map.
> To prevent this, a rollback mechanism (with proper logging) should be 
> implemented.  It would also make sense to do more sanity/consistency check in 
> the Oozie server.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] Subscription: Oozie Patch Available

[jira] Subscription: Oozie Patch Available

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config

Re: [VOTE] Release Oozie 4.3.1(candidate 4)

[jira] [Commented] (OOZIE-3163) Improve documentation rendering: use fluido skin and better config

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

Failed: OOZIE-3173 PreCommit Build #383

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

Failed: OOZIE-3173 PreCommit Build #382

[jira] [Updated] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

Re: Review Request 65535: OOZIE-3173 Coordinator job with frequency using cron syntax creates only one action in catchup mode

[jira] [Commented] (OOZIE-3173) Coordinator job with frequency using cron syntax creates only one action in catchup mode

Re: Review Request 64029: OOZIE-2339 Provide an API for writing jobs based on the XSD schemas

[jira] [Assigned] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[jira] [Created] (OOZIE-3178) ./bin/mkdistro.sh -Papache-release fails due to javadoc errors

[jira] [Assigned] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Commented] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Created] (OOZIE-3177) Unclear ooziedb -sqlFile option behaviour

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Commented] (OOZIE-3172) Upgrade non-transitive Jackson dependencies from org.codehaus.jackson to com.fasterxml.jackson

[jira] [Updated] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Created] (OOZIE-3176) Oozie-core fails with checkstyle errors.

[jira] [Commented] (OOZIE-3134) Potential inconsistency between the in-memory SLA map and the Oozie database

28 matches

Site Navigation

Mail list logo

Footer information