[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (106 issues) Subscriber: ooziedaily Key Summary OOZIE-3182 Oozie components fail with checkstyle errors https://issues.apache.org/jira/browse/OOZIE-3182 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3176 Oozie-core fails with checkstyle errors. https://issues.apache.org/jira/browse/OOZIE-3176 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 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-3109 Escape log-streaming's HTML-specific characters https://issues.apache.org/jira/browse/OOZIE-3109 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.apach
[jira] [Created] (OOZIE-3185) Conflicting JARs org.apache.derby exist in Oozie
PandaMonkey created OOZIE-3185: -- Summary: Conflicting JARs org.apache.derby exist in Oozie Key: OOZIE-3185 URL: https://issues.apache.org/jira/browse/OOZIE-3185 Project: Oozie Issue Type: Bug Components: core Affects Versions: 5.0.0b1 Reporter: PandaMonkey Fix For: 5.0.0 Attachments: oozie.txt Hi, by analyzing oozie-master\core\pom.xml, I found that there are two versions of org.apache.derby:derby. Their introduced path is: 1. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile 2. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct dependency. By further analyzing the source code, *we found they have too many different features*. Also, I found that you have already gave derby a exclusion tag when transitively introducing derby by hive-beeline to avoid dependency conflict. So it would be nice to keep the consistency of library version for the project long-term health, maybe update org.apache.derby:derby from 10.10.1.1 to 10.11.1.1, or exclude derby from hive-exec is a good choice. Hope this can help you. Thanks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OOZIE-3185) Conflicting JARs org.apache.derby exist in Oozie
[ https://issues.apache.org/jira/browse/OOZIE-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated OOZIE-3185: --- Attachment: oozie.txt > Conflicting JARs org.apache.derby exist in Oozie > > > Key: OOZIE-3185 > URL: https://issues.apache.org/jira/browse/OOZIE-3185 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.0.0b1 >Reporter: PandaMonkey >Priority: Major > Fix For: 5.0.0 > > Attachments: oozie.txt > > > Hi, by analyzing oozie-master\core\pom.xml, I found that there are two > versions of org.apache.derby:derby. Their introduced paths are: > 1. > org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile > 2. > org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile > Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by > org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct > dependency. By further analyzing the source code, *we found they have too > many different features*. > Also, I found that you have already gave derby a exclusion tag when > transitively introducing derby by hive-beeline to avoid dependency conflict. > So it would be nice to keep the consistency of library version for the > project long-term health, maybe *update org.apache.derby:derby from 10.10.1.1 > to 10.11.1.1, or exclude derby from hive-exec* is a good choice. Hope this > can help you. Thanks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OOZIE-3185) Conflicting JARs org.apache.derby exist in Oozie
[ https://issues.apache.org/jira/browse/OOZIE-3185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] PandaMonkey updated OOZIE-3185: --- Description: Hi, by analyzing oozie-master\core\pom.xml, I found that there are two versions of org.apache.derby:derby. Their introduced path is: 1. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile 2. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct dependency. By further analyzing the source code, *we found they have too many different features*. Also, I found that you have already gave derby a exclusion tag when transitively introducing derby by hive-beeline to avoid dependency conflict. So it would be nice to keep the consistency of library version for the project long-term health, maybe *update org.apache.derby:derby from 10.10.1.1 to 10.11.1.1, or exclude derby from hive-exec* is a good choice. Hope this can help you. Thanks. was: Hi, by analyzing oozie-master\core\pom.xml, I found that there are two versions of org.apache.derby:derby. Their introduced path is: 1. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile 2. org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct dependency. By further analyzing the source code, *we found they have too many different features*. Also, I found that you have already gave derby a exclusion tag when transitively introducing derby by hive-beeline to avoid dependency conflict. So it would be nice to keep the consistency of library version for the project long-term health, maybe update org.apache.derby:derby from 10.10.1.1 to 10.11.1.1, or exclude derby from hive-exec is a good choice. Hope this can help you. Thanks. > Conflicting JARs org.apache.derby exist in Oozie > > > Key: OOZIE-3185 > URL: https://issues.apache.org/jira/browse/OOZIE-3185 > Project: Oozie > Issue Type: Bug > Components: core >Affects Versions: 5.0.0b1 >Reporter: PandaMonkey >Priority: Major > Fix For: 5.0.0 > > Attachments: oozie.txt > > > Hi, by analyzing oozie-master\core\pom.xml, I found that there are two > versions of org.apache.derby:derby. Their introduced path is: > 1. > org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.derby:derby:10.10.1.1::compile > 2. > org.apache.oozie:oozie-core:5.0.0-beta1::null->org.apache.hive:hive-exec:1.2.0:core:compile->org.apache.hive:hive-metastore:1.2.0::compile->org.apache.derby:derby:10.11.1.1::compile > Of them, org.apache.derby:derby:10.10.1.1 is the transitively introduced by > org.apache.hive:hive-exec and org.apache.derby:derby:10.11.1.1 is the direct > dependency. By further analyzing the source code, *we found they have too > many different features*. > Also, I found that you have already gave derby a exclusion tag when > transitively introducing derby by hive-beeline to avoid dependency conflict. > So it would be nice to keep the consistency of library version for the > project long-term health, maybe *update org.apache.derby:derby from 10.10.1.1 > to 10.11.1.1, or exclude derby from hive-exec* is a good choice. Hope this > can help you. Thanks. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
