[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
[
https://issues.apache.org/jira/browse/OOZIE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811466#comment-16811466
]
Andras Salamon commented on OOZIE-3463:
---
Thanks [~nobigo] for the very quick patch. I'll check it in more details, can
you please address the "the patch contains 5 line(s) longer than 132
characters" warning in the meantime?
> Migrate from com.google.common.base.Charsets to
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
> Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
[
https://issues.apache.org/jira/browse/OOZIE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811440#comment-16811440
]
Hadoop QA commented on OOZIE-3463:
--
Testing JIRA OOZIE-3463
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{color:red}-1{color} the patch contains 5 line(s) longer than 132
characters
.{color:green}+1{color} the patch adds/modifies 2 testcase(s)
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:green}+1 JAVADOC{color}
.{color:green}+1{color} Javadoc generation succeeded with the patch
.{color:green}+1{color} the patch does not seem to introduce new 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:red}-1{color} There are [15] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [examples].
.{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/hcatalog].
.{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 [sharelib/spark].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:red}-1{color} There are [15] new bugs found below threshold in
[tools] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
tools/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At OozieDBCLI.java:[line 578]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 568]: At OozieDBCLI.java:[line 567]
.At OozieDBCLI.java:[line 571]: At OozieDBCLI.java:[line 569]
.At OozieDBCLI.java:[line 573]: At OozieDBCLI.java:[line 572]
.At OozieDBCLI.java:[line 578]: At OozieDBCLI.java:[line 575]
.{color:green}+1{color} There are no new bugs found in [core].
.{color:orange}0{color} There are [4] new bugs found in [server] that would
be nice to have fixed.
.You can find the SpotBugs diff here: server/findbugs-new.html
{color:green}+1 BACKWARDS_COMPATIBILITY{color}
.{color:green}+1{color} the patch does not change any JPA
Entity/Colum/Basic/Lob/Transient annotations
.{color:green}+1{color} the patch does not modify JPA files
{color:green}+1 TESTS{color}
.Tests run: 3169
.{color:orange}Tests failed at first run:{color}
TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator
.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}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/1077/
> Migrate from com.google.common.base.Charsets to
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
> Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
> class as suggested
Failed: OOZIE-3463 PreCommit Build #1077
Jira: https://issues.apache.org/jira/browse/OOZIE-3463 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1077/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.93 MB...] [DEBUG] There are no new bugs found in [core]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [WARN] There are [4] new bugs found in [server]. [DEBUG] You can find the SpotBugs diff here: server/findbugs-new.html [ERROR] There are [15] new bugs found below threshold in total that must be fixed. [TRACE] SpotBugs diffs checked and reports created [TRACE] Summary file size is 3292 bytes [TRACE] Full summary file size is 6701 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Testing JIRA OOZIE-3463 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 star imports -1 the patch contains 5 line(s) longer than 132 characters +1 the patch adds/modifies 2 testcase(s) +1 RAT +1 the patch does not seem to introduce new RAT warnings +1 JAVADOC +1 Javadoc generation succeeded with the patch +1 the patch does not seem to introduce new 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 [15] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/hcatalog]. +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 [sharelib/spark]. +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/streaming]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [webapp]. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [docs]. -1 There are [15] new bugs found below threshold in [tools] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): tools/findbugs-new.html The top [5] most important SpotBugs errors are: At OozieDBCLI.java:[line 578]: This use of java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL injection At OozieDBCLI.java:[line 568]: At OozieDBCLI.java:[line 567] At OozieDBCLI.java:[line 571]: At OozieDBCLI.java:[line 569] At OozieDBCLI.java:[line 573]: At OozieDBCLI.java:[line 572] At OozieDBCLI.java:[line 578]: At OozieDBCLI.java:[line 575] +1 There are no new bugs found in [core]. 0 There are [4] new bugs found in [server] that would be nice to have fixed. You can find the SpotBugs diff here: server/findbugs-new.html +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: 3169 Tests failed at first run: TestBundleChangeXCommand#testBundlePauseExtendMaterializesCoordinator 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) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1077/ 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 --:--:-- --:--:-- --:--:--
[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
[
https://issues.apache.org/jira/browse/OOZIE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811406#comment-16811406
]
Hadoop QA commented on OOZIE-3463:
--
PreCommit-OOZIE-Build started
> Migrate from com.google.common.base.Charsets to
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
> Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
[
https://issues.apache.org/jira/browse/OOZIE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16811386#comment-16811386
]
duan xiong commented on OOZIE-3463:
---
Hi,[~asalamon74],Can you help me review this.Thank you !
> Migrate from com.google.common.base.Charsets to
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
> Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
[
https://issues.apache.org/jira/browse/OOZIE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
duan xiong updated OOZIE-3463:
--
Attachment: OOZIE-3463-001.patch
> Migrate from com.google.common.base.Charsets to
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
> Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
> Attachments: OOZIE-3463-001.patch
>
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
[
https://issues.apache.org/jira/browse/OOZIE-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
duan xiong reassigned OOZIE-3463:
-
Assignee: duan xiong
> Migrate from com.google.common.base.Charsets to
> java.nio.charset.StandardCharsets
> -
>
> Key: OOZIE-3463
> URL: https://issues.apache.org/jira/browse/OOZIE-3463
> Project: Oozie
> Issue Type: Improvement
>Reporter: Andras Salamon
>Assignee: duan xiong
>Priority: Major
>
> Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
> 1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
> class as suggested [here|https://stackoverflow.com/a/16066990/21348].
> We should also {{name()}} instead of {{toString()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (OOZIE-3458) Can no longer submit a coordinator job which has oozie.libpath and oozie.coord.application.path set
[
https://issues.apache.org/jira/browse/OOZIE-3458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
duan xiong updated OOZIE-3458:
--
Attachment: OOZIE-3463-001.patch
> Can no longer submit a coordinator job which has oozie.libpath and
> oozie.coord.application.path set
> ---
>
> Key: OOZIE-3458
> URL: https://issues.apache.org/jira/browse/OOZIE-3458
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Jerry Chabot
>Priority: Critical
> Attachments: OOZIE-3463-001.patch
>
>
> This bug is related to https://issues.apache.org/jira/browse/OOZIE-3457. Our
> Production environment is currently running Amazon EMR 5.19. We want to
> upgrade to EMR 5.22. Oozie will be upgraded from 5.0.0 to 5.1.0. Our
> deployment scripts can no longer submit coordinator jobs after upgrading a
> test environment. Here is a sample post from the oozie client.
> POST [http://hbase.qa.local:11000/oozie/v2/jobs?action=start]
>
> nameNodehdfs://hbase.qa.local:8020
> oozie.use.system.libpathtrue
> startTime2018-03-28T00:00Z
> queueNameoozie
> jobTrackerhbase.qa.local:8032
> oozie.libpathhdfs://hbase.qa.local:8020/user/oozie/cmx
> endTime2020-01-01:00Z
> applicationConfigFilehdfs://hbase.qa.local:8020/usr/share/cmx/conf/app.properties,hdfs://hbase.qa.local:8020/usr/share/cmx/conf/crypto.properties
> frequency240
> user.nameoozie
> oozie.coord.application.pathhdfs://hbase.qa.local:8020/user/oozie/reporting/workspaceDimToVertica/
>
> Error: E0307 : E0307: Runtime error [App directory [null] does not exist and
> app definition cannot be created because of missing config value
> [oozie.jobs.api.generated.xml]]
> Note, our code specifies oozie.libpath and oozie.coord.application.path. Is
> this no longer allowed?
> I've narrowed down the problem to the checkAndWriteApplicationXMLToHDFS(...)
> method in V1JobsServlet.java. It is related to the new feature for submitting
> embedded XML within the job submission. This method is check whether the
> workflow.xml or coodinator.xml exists in either oozie.wf.application.path,
> oozie.libpath, oozie.coord.application.path or oozie.bundle.application.path.
> First, why is it checking oozie.libpath? That is not an application path.
> Second, it stops looking as soon as findAppPathsWithFileNames() returns a
> value. Which it will always do when oozie.libpath is set even if an xml
> doesn't exist there. It does not continue looking for an xml file in
> oozie.coord.application.path or oozie.bundle.application.path. I realize
> only one application path should be specified. IIMO, its the oozie.libpath
> check that is the problem.
> Third, the logic is inefficient. Here are two lines. Why call the same method
> again with the same params. You already have the result!
> if (!findAppPathsWithFileNames(appPath, "workflow.xml").isEmpty()) {
> appPathsWithFileNames = findAppPathsWithFileNames(appPath, "workflow.xml");
> }
> It is critical that we upgrade to EMR 5.22. However, we are blocked until we
> figure out a way to get the job submitted and completing successfully. Any
> suggested workarounds would be greatly appreciated. But, I am filing this bug
> to get it fixed so an upgraded Oozie will make it into a future EMR release.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3328) Create Hive compatibility action executor to run hive actions using beeline
[
https://issues.apache.org/jira/browse/OOZIE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810954#comment-16810954
]
Hadoop QA commented on OOZIE-3328:
--
Testing JIRA OOZIE-3328
Cleaning local git workspace
{color:green}+1 PATCH_APPLIES{color}
{color:green}+1 CLEAN{color}
{color:red}-1 RAW_PATCH_ANALYSIS{color}
.{color:green}+1{color} the patch does not introduce any @author tags
.{color:green}+1{color} the patch does not introduce any tabs
.{color:green}+1{color} the patch does not introduce any trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{color:red}-1{color} the patch contains 1 line(s) longer than 132
characters
.{color:red}-1{color} the patch does not add/modify any testcase
{color:green}+1 RAT{color}
.{color:green}+1{color} the patch does not seem to introduce new RAT
warnings
{color:red}-1 JAVADOC{color}
.{color:red}-1{color} build with Javadoc generation fails with the patch
{color:red}-1 COMPILE{color}
.{color:green}+1{color} HEAD compiles
.{color:red}-1{color} patch does not compile
.{color:green}+1{color} the patch does not seem to introduce new javac
warnings
{color:red}-1{color} There are [8] new bugs found below threshold in total that
must be fixed.
.{color:green}+1{color} There are no new bugs found in
[fluent-job/fluent-job-api].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:red}-1{color} There are [8] new bugs found below threshold in
[core] that must be fixed, listing only the first [5] ones.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The top [5] most important SpotBugs errors are:
.At HiveCredentials.java:[line 98]: Exception is caught when Exception is
not thrown in
org.apache.oozie.action.hadoop.HiveCredentials.updateCredentials(Credentials,
Configuration, CredentialsProperties, ActionExecutor$Context)
.At BulkJPAExecutor.java:[line 207]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176]
.At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207]
.{color:green}+1{color} There are no new bugs found in [server].
.{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/oozie].
.{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/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/git].
.{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/sqoop].
.{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/streaming].
.{color:green}+1{color} There are no new bugs found in [sharelib/hcatalog].
.{color:green}+1{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [tools].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:green}+1{color} There are no new bugs found in [webapp].
{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} - patch does not compile, cannot run test cases
.{color:orange}Tests failed at first run:{color}
TestCoordActionInputCheckXCommand#testNone
.For the complete list of flaky tests, see TEST-SUMMARY-FULL files.
{color:red}-1 DISTRO{color}
.{color:red}-1{color} distro tarball fails with the patch
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://builds.apache.org/job/PreCommit-OOZIE-Build/1076/
> Create Hive compatibility action executor to run hive actions using beeline
> ---
>
> Key: OOZIE-3328
> URL: https://issues.apache.org/jira/browse/OOZIE-3328
> Project: Oozie
> Issue Type: Task
> Components: action, core
>Affects Versions: 5.0.0, 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Major
> Labels: features,
Failed: OOZIE-3328 PreCommit Build #1076
Jira: https://issues.apache.org/jira/browse/OOZIE-3328 Build: https://builds.apache.org/job/PreCommit-OOZIE-Build/1076/ ### ## LAST 100 LINES OF THE CONSOLE ### [...truncated 1.67 MB...] [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [examples]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [tools]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [client]. [TRACE] New XMLLib present, calling 'xmllint --xpath' to get bug instance counts [DEBUG] There are no new bugs found in [webapp]. [ERROR] There are [8] new bugs found below threshold in total that must be fixed. [TRACE] SpotBugs diffs checked and reports created [TRACE] Summary file size is 3457 bytes [TRACE] Full summary file size is 4507 bytes [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar] removed [TRACE] File [/home/jenkins/jenkins-slave/workspace/PreCommit-OOZIE-Build/test-patch/tmp/SPOTBUGS_DIFF/diff/findbugs-diff-0.1.0-all.jar.md5] removed Running test-patch task BACKWARDS_COMPATIBILITY Running test-patch task TESTS Running test-patch task DISTRO Testing JIRA OOZIE-3328 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 star imports -1 the patch contains 1 line(s) longer than 132 characters -1 the patch does not add/modify any testcase +1 RAT +1 the patch does not seem to introduce new RAT warnings -1 JAVADOC -1 build with Javadoc generation fails with the patch -1 COMPILE +1 HEAD compiles -1 patch does not compile +1 the patch does not seem to introduce new javac warnings -1 There are [8] new bugs found below threshold in total that must be fixed. +1 There are no new bugs found in [fluent-job/fluent-job-api]. +1 There are no new bugs found in [docs]. -1 There are [8] new bugs found below threshold in [core] that must be fixed, listing only the first [5] ones. You can find the SpotBugs diff here (look for the red and orange ones): core/findbugs-new.html The top [5] most important SpotBugs errors are: At HiveCredentials.java:[line 98]: Exception is caught when Exception is not thrown in org.apache.oozie.action.hadoop.HiveCredentials.updateCredentials(Credentials, Configuration, CredentialsProperties, ActionExecutor$Context) At BulkJPAExecutor.java:[line 207]: This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection At BulkJPAExecutor.java:[line 177]: At BulkJPAExecutor.java:[line 176] At BulkJPAExecutor.java:[line 206]: At BulkJPAExecutor.java:[line 200] This use of javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query; can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 207] +1 There are no new bugs found in [server]. +1 There are no new bugs found in [sharelib/distcp]. +1 There are no new bugs found in [sharelib/oozie]. +1 There are no new bugs found in [sharelib/hive]. +1 There are no new bugs found in [sharelib/hive2]. +1 There are no new bugs found in [sharelib/git]. +1 There are no new bugs found in [sharelib/spark]. +1 There are no new bugs found in [sharelib/sqoop]. +1 There are no new bugs found in [sharelib/pig]. +1 There are no new bugs found in [sharelib/streaming]. +1 There are no new bugs found in [sharelib/hcatalog]. +1 There are no new bugs found in [examples]. +1 There are no new bugs found in [tools]. +1 There are no new bugs found in [client]. +1 There are no new bugs found in [webapp]. +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 - patch does not compile, cannot run test cases Tests failed at first run: TestCoordActionInputCheckXCommand#testNone For the complete list of flaky tests, see TEST-SUMMARY-FULL files. -1 DISTRO -1 distro tarball fails with the patch -1 Overall result, please check the reported -1(s) The full output of the test-patch run is available at https://builds.apache.org/job/PreCommit-OOZIE-Build/1076/ Adding comment to JIRA % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 0
[jira] [Created] (OOZIE-3463) Migrate from com.google.common.base.Charsets to java.nio.charset.StandardCharsets
Andras Salamon created OOZIE-3463:
-
Summary: Migrate from com.google.common.base.Charsets to
java.nio.charset.StandardCharsets
Key: OOZIE-3463
URL: https://issues.apache.org/jira/browse/OOZIE-3463
Project: Oozie
Issue Type: Improvement
Reporter: Andras Salamon
Oozie uses {{com.google.common.base.Charsets}} in several places. Since Java
1.7 it's much easier to use the builtin {{java.nio.charset.StandardCharsets}}
class as suggested [here|https://stackoverflow.com/a/16066990/21348].
We should also {{name()}} instead of {{toString()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3418) Upgrade to Guava 27
[ https://issues.apache.org/jira/browse/OOZIE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810882#comment-16810882 ] Andras Salamon commented on OOZIE-3418: --- In the meantime Guava 27.1 has been released. > Upgrade to Guava 27 > --- > > Key: OOZIE-3418 > URL: https://issues.apache.org/jira/browse/OOZIE-3418 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: Andras Salamon >Assignee: Andras Salamon >Priority: Major > Attachments: OOZIE-3418-01-WIP.patch > > > There is a guava security issue: > [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237] > Currently we use Guava 11.0.2 which is affected. We need to upgrade to at > least guava 24.1.1. Probably the best would be to use Guava 27. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3328) Create Hive compatibility action executor to run hive actions using beeline
[ https://issues.apache.org/jira/browse/OOZIE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810850#comment-16810850 ] Hadoop QA commented on OOZIE-3328: -- PreCommit-OOZIE-Build started > Create Hive compatibility action executor to run hive actions using beeline > --- > > Key: OOZIE-3328 > URL: https://issues.apache.org/jira/browse/OOZIE-3328 > Project: Oozie > Issue Type: Task > Components: action, core >Affects Versions: 5.0.0, 4.3.1 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Major > Labels: features, usability > Attachments: OOZIE-3328.001.patch > > > If I am correct then Hive will not support HiveCli for long and Oozie may > have to handle this. > A new executor shall be created which can understand the original hive action > format while this executor shall run the action using beeline. > What are your thoughts? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3418) Upgrade to Guava 27
[
https://issues.apache.org/jira/browse/OOZIE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810837#comment-16810837
]
Andras Salamon commented on OOZIE-3418:
---
I think it would be useful to avoid writing code which is guava version
specific. So maybe it would be better to make separate jiras which change the
code in a way that it's compatible with both Guava 11 and Guava 27. Those jiras
could be committed before we increase the guava version and this Jira could
focus on pom changes and shading. Two possible jiras:
* Eliminate com.google.common.io.Closeables and replace it by commons-io
IOUtils like in the patch.
* Eliminate com.google.common.base.Stopwatch and replace by commons-lang
Stopwatch, hadoop stopwatch, or simple {{System.nanoTime()}} calls.
> Upgrade to Guava 27
> ---
>
> Key: OOZIE-3418
> URL: https://issues.apache.org/jira/browse/OOZIE-3418
> Project: Oozie
> Issue Type: Bug
>Affects Versions: 5.1.0
>Reporter: Andras Salamon
>Assignee: Andras Salamon
>Priority: Major
> Attachments: OOZIE-3418-01-WIP.patch
>
>
> There is a guava security issue:
> [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237]
> Currently we use Guava 11.0.2 which is affected. We need to upgrade to at
> least guava 24.1.1. Probably the best would be to use Guava 27.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (OOZIE-3283) Prototyping: create React workflow list page
[ https://issues.apache.org/jira/browse/OOZIE-3283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810817#comment-16810817 ] Thai Bui commented on OOZIE-3283: - Hey [~andras.piros]! Yes. The wireframe definitely helps. I'm not sure about the addition of the search results separated from the other boxes in the wireframe though. The rest I think is a good start for us. > Prototyping: create React workflow list page > > > Key: OOZIE-3283 > URL: https://issues.apache.org/jira/browse/OOZIE-3283 > Project: Oozie > Issue Type: Sub-task >Reporter: Andras Piros >Assignee: Thai Bui >Priority: Major > Attachments: Screen Shot 2018-06-14 at 9.24.46 AM.png, Screen Shot > 2018-06-14 at 9.25.42 AM.png > > > Create a [*React*|https://redux.js.org/basics/usage-with-react] / > [*Redux*|https://redux.js.org/basics/usage-with-react] prototype of the > workflow list page. Don't have to handle authentication / authorization for > now. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (OOZIE-3328) Create Hive compatibility action executor to run hive actions using beeline
[ https://issues.apache.org/jira/browse/OOZIE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810778#comment-16810778 ] Denes Bodo edited comment on OOZIE-3328 at 4/5/19 12:55 PM: The suggested implementation needs Hive3 as dependency due to the used beeline-site.xml location. I am uploading the diff here and to [RB|https://reviews.apache.org/r/70406/]. CC [~matijhs] was (Author: dionusos): The suggested implementation needs Hive3 as dependency due to the used beeline-site.xml location. I am uploading the diff here and to [RB|https://reviews.apache.org/r/70406/]. > Create Hive compatibility action executor to run hive actions using beeline > --- > > Key: OOZIE-3328 > URL: https://issues.apache.org/jira/browse/OOZIE-3328 > Project: Oozie > Issue Type: Task > Components: action, core >Affects Versions: 5.0.0, 4.3.1 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Major > Labels: features, usability > Attachments: OOZIE-3328.001.patch > > > If I am correct then Hive will not support HiveCli for long and Oozie may > have to handle this. > A new executor shall be created which can understand the original hive action > format while this executor shall run the action using beeline. > What are your thoughts? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OOZIE-3328) Create Hive compatibility action executor to run hive actions using beeline
[ https://issues.apache.org/jira/browse/OOZIE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Denes Bodo updated OOZIE-3328: -- Attachment: OOZIE-3328.001.patch > Create Hive compatibility action executor to run hive actions using beeline > --- > > Key: OOZIE-3328 > URL: https://issues.apache.org/jira/browse/OOZIE-3328 > Project: Oozie > Issue Type: Task > Components: action, core >Affects Versions: 5.0.0, 4.3.1 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Major > Labels: features, usability > Attachments: OOZIE-3328.001.patch > > > If I am correct then Hive will not support HiveCli for long and Oozie may > have to handle this. > A new executor shall be created which can understand the original hive action > format while this executor shall run the action using beeline. > What are your thoughts? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-3328) Create Hive compatibility action executor to run hive actions using beeline
[ https://issues.apache.org/jira/browse/OOZIE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810778#comment-16810778 ] Denes Bodo commented on OOZIE-3328: --- The suggested implementation needs Hive3 as dependency due to the used beeline-site.xml location. I am uploading the diff here and to [RB|https://reviews.apache.org/r/70406/]. > Create Hive compatibility action executor to run hive actions using beeline > --- > > Key: OOZIE-3328 > URL: https://issues.apache.org/jira/browse/OOZIE-3328 > Project: Oozie > Issue Type: Task > Components: action, core >Affects Versions: 5.0.0, 4.3.1 >Reporter: Denes Bodo >Assignee: Denes Bodo >Priority: Major > Labels: features, usability > > If I am correct then Hive will not support HiveCli for long and Oozie may > have to handle this. > A new executor shall be created which can understand the original hive action > format while this executor shall run the action using beeline. > What are your thoughts? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (OOZIE-3204) Oozie cannot run HBase code in Java action
[
https://issues.apache.org/jira/browse/OOZIE-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denes Bodo resolved OOZIE-3204.
---
Resolution: Invalid
> Oozie cannot run HBase code in Java action
> ---
>
> Key: OOZIE-3204
> URL: https://issues.apache.org/jira/browse/OOZIE-3204
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
>
> After having custom raw file system implementation, HBase (java) action
> cannot run:
> {noformat}
> 018-03-28 06:55:46,372 WARN HbaseCredentials:523 -
> SERVER[ctr-e138-1518143905142-137559-01-03.hwx.site] USER[hrt_qa]
> GROUP[-] TOKEN[] APP[tpch_query1] JOB[002-180328065157516-oozie-oozi-W]
> ACTION[002-180328065157516-oozie-oozi-W@tpch_query1] Exception in
> receiving hbase credentials
> java.io.IOException: java.lang.reflect.InvocationTargetException
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> at
> org.apache.hadoop.hbase.security.token.TokenUtil.obtainToken(TokenUtil.java:68)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:86)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:84)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1869)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:313)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials.obtainToken(HbaseCredentials.java:83)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials.addtoJobConf(HbaseCredentials.java:56)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1338)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1178)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1424)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> ... 24 more
> Caused by: java.lang.ExceptionInInitializerError
> at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
> at
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:903)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
> ... 29 more
> Caused by: java.lang.UnsupportedOperationException: Accessing local file
> system is not allowed
> at
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
> at
> org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
> at
>
[jira] [Assigned] (OOZIE-3204) Oozie cannot run HBase code in Java action
[
https://issues.apache.org/jira/browse/OOZIE-3204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denes Bodo reassigned OOZIE-3204:
-
Assignee: Denes Bodo
> Oozie cannot run HBase code in Java action
> ---
>
> Key: OOZIE-3204
> URL: https://issues.apache.org/jira/browse/OOZIE-3204
> Project: Oozie
> Issue Type: Bug
> Components: core
>Affects Versions: 4.3.1
>Reporter: Denes Bodo
>Assignee: Denes Bodo
>Priority: Critical
>
> After having custom raw file system implementation, HBase (java) action
> cannot run:
> {noformat}
> 018-03-28 06:55:46,372 WARN HbaseCredentials:523 -
> SERVER[ctr-e138-1518143905142-137559-01-03.hwx.site] USER[hrt_qa]
> GROUP[-] TOKEN[] APP[tpch_query1] JOB[002-180328065157516-oozie-oozi-W]
> ACTION[002-180328065157516-oozie-oozi-W@tpch_query1] Exception in
> receiving hbase credentials
> java.io.IOException: java.lang.reflect.InvocationTargetException
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:240)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:218)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:119)
> at
> org.apache.hadoop.hbase.security.token.TokenUtil.obtainToken(TokenUtil.java:68)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:86)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials$1.run(HbaseCredentials.java:84)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:422)
> at
> org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1869)
> at
> org.apache.hadoop.hbase.security.User$SecureHadoopUser.runAs(User.java:313)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials.obtainToken(HbaseCredentials.java:83)
> at
> org.apache.oozie.action.hadoop.HbaseCredentials.addtoJobConf(HbaseCredentials.java:56)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.setCredentialTokens(JavaActionExecutor.java:1338)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.submitLauncher(JavaActionExecutor.java:1178)
> at
> org.apache.oozie.action.hadoop.JavaActionExecutor.start(JavaActionExecutor.java:1424)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:234)
> at
> org.apache.oozie.command.wf.ActionStartXCommand.execute(ActionStartXCommand.java:65)
> at org.apache.oozie.command.XCommand.call(XCommand.java:287)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:331)
> at
> org.apache.oozie.service.CallableQueueService$CompositeCallable.call(CallableQueueService.java:260)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at
> org.apache.oozie.service.CallableQueueService$CallableWrapper.run(CallableQueueService.java:178)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at
> org.apache.hadoop.hbase.client.ConnectionFactory.createConnection(ConnectionFactory.java:238)
> ... 24 more
> Caused by: java.lang.ExceptionInInitializerError
> at org.apache.hadoop.hbase.ClusterId.parseFrom(ClusterId.java:64)
> at
> org.apache.hadoop.hbase.zookeeper.ZKClusterId.readClusterIdZNode(ZKClusterId.java:75)
> at
> org.apache.hadoop.hbase.client.ZooKeeperRegistry.getClusterId(ZooKeeperRegistry.java:105)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.retrieveClusterId(ConnectionManager.java:903)
> at
> org.apache.hadoop.hbase.client.ConnectionManager$HConnectionImplementation.(ConnectionManager.java:648)
> ... 29 more
> Caused by: java.lang.UnsupportedOperationException: Accessing local file
> system is not allowed
> at
> org.apache.hadoop.fs.RawLocalFileSystem.initialize(RawLocalFileSystem.java:48)
> at
> org.apache.hadoop.fs.LocalFileSystem.initialize(LocalFileSystem.java:47)
> at
>
[jira] [Commented] (OOZIE-3418) Upgrade to Guava 27
[ https://issues.apache.org/jira/browse/OOZIE-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810665#comment-16810665 ] Andras Salamon commented on OOZIE-3418: --- I've checked the status of Guava update in Hadoop. The main jira: HADOOP-15960 Upgrade has already been committed to trunk (3.3), it will also be committed soon to 3.0, 3.1, 3.2: HADOOP-16211, HADOOP-16212, HADOOP-16213. Since the latest Guava versions don't support Java7, the upgrade will be more difficult for hadoop-2. It will be committed to the 2.7 branch first. Unfortunately Oozie does not support hadoop-3 yet ( OOZIE-2973 ). > Upgrade to Guava 27 > --- > > Key: OOZIE-3418 > URL: https://issues.apache.org/jira/browse/OOZIE-3418 > Project: Oozie > Issue Type: Bug >Affects Versions: 5.1.0 >Reporter: Andras Salamon >Assignee: Andras Salamon >Priority: Major > Attachments: OOZIE-3418-01-WIP.patch > > > There is a guava security issue: > [CVE-2018-10237|https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10237] > Currently we use Guava 11.0.2 which is affected. We need to upgrade to at > least guava 24.1.1. Probably the best would be to use Guava 27. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (OOZIE-2052) TestAbandonedCoordChecker.testMessage_withMixedStatus is flaky
[ https://issues.apache.org/jira/browse/OOZIE-2052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andras Salamon updated OOZIE-2052: -- Issue Type: Sub-task (was: Bug) Parent: OOZIE-3111 > TestAbandonedCoordChecker.testMessage_withMixedStatus is flaky > -- > > Key: OOZIE-2052 > URL: https://issues.apache.org/jira/browse/OOZIE-2052 > Project: Oozie > Issue Type: Sub-task >Reporter: Purshotam Shah >Assignee: Purshotam Shah >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (OOZIE-1169) Investigate replacing ParamChecker with Google Guava's Preconditions
[
https://issues.apache.org/jira/browse/OOZIE-1169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16810590#comment-16810590
]
Andras Salamon commented on OOZIE-1169:
---
It seems to me, Oozie still use its own ParamChecker, but already started to
use Guava's Preconditions as well.
> Investigate replacing ParamChecker with Google Guava's Preconditions
>
>
> Key: OOZIE-1169
> URL: https://issues.apache.org/jira/browse/OOZIE-1169
> Project: Oozie
> Issue Type: Bug
>Affects Versions: trunk
>Reporter: Robert Kanter
>Priority: Minor
>
> We currently use our own {{ParamChecker}} class to check/verify arguments for
> some of the methods. We should investigate if it makes sense to use [Google
> Guava's
> Preconditions|http://docs.guava-libraries.googlecode.com/git/javadoc/com/google/common/base/Preconditions.html]
> instead (or some other library).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] Subscription: Oozie Patch Available
Issue Subscription Filter: Oozie Patch Available (90 issues) Subscriber: ooziedaily Key Summary OOZIE-3461 CoordMaterializeTriggerService code cleanup https://issues.apache.org/jira/browse/OOZIE-3461 OOZIE-3455 Inconsistent CoordMaterializeTransitionXCommand logging https://issues.apache.org/jira/browse/OOZIE-3455 OOZIE-3449 Make spark-2 as the default profile https://issues.apache.org/jira/browse/OOZIE-3449 OOZIE-3447 Run test case in local : It shows oozie-hsqldb-orm.xml exception https://issues.apache.org/jira/browse/OOZIE-3447 OOZIE-3418 Upgrade to Guava 27 https://issues.apache.org/jira/browse/OOZIE-3418 OOZIE-3404 The env variable of SPARK_HOME needs to be set when running pySpark https://issues.apache.org/jira/browse/OOZIE-3404 OOZIE-3375 Can't use empty in coordinator https://issues.apache.org/jira/browse/OOZIE-3375 OOZIE-3367 Using && in EL expressions in oozie bundle.xml files generates parse errors https://issues.apache.org/jira/browse/OOZIE-3367 OOZIE-3366 Update workflow status and subworkflow status on suspend command https://issues.apache.org/jira/browse/OOZIE-3366 OOZIE-3364 Rerunning Oozie bundle jobs starts the coordinators in indeterminate order https://issues.apache.org/jira/browse/OOZIE-3364 OOZIE-3362 When killed, SSH action should kill the spawned processes on target host https://issues.apache.org/jira/browse/OOZIE-3362 OOZIE-3335 Cleanup parseFilter methods https://issues.apache.org/jira/browse/OOZIE-3335 OOZIE-3320 Oozie ShellAction should support absolute bash file path https://issues.apache.org/jira/browse/OOZIE-3320 OOZIE-3319 Log SSH action callback error output https://issues.apache.org/jira/browse/OOZIE-3319 OOZIE-3301 Update NOTICE file https://issues.apache.org/jira/browse/OOZIE-3301 OOZIE-3274 Remove slf4j https://issues.apache.org/jira/browse/OOZIE-3274 OOZIE-3266 Coord action rerun support RERUN_SKIP_NODES option https://issues.apache.org/jira/browse/OOZIE-3266 OOZIE-3265 properties RERUN_FAIL_NODES and RERUN_SKIP_NODES should be able to appear together https://issues.apache.org/jira/browse/OOZIE-3265 OOZIE-3256 refactor OozieCLI class https://issues.apache.org/jira/browse/OOZIE-3256 OOZIE-3249 [tools] Instrumentation log parser https://issues.apache.org/jira/browse/OOZIE-3249 OOZIE-3199 Let system property restriction configurable https://issues.apache.org/jira/browse/OOZIE-3199 OOZIE-3196 Authorization: restrict world readability by user https://issues.apache.org/jira/browse/OOZIE-3196 OOZIE-3179 Adding a configurable config-default.xml location to a workflow https://issues.apache.org/jira/browse/OOZIE-3179 OOZIE-3170 Oozie Diagnostic Bundle tool fails with NPE due to missing service class https://issues.apache.org/jira/browse/OOZIE-3170 OOZIE-3137 Add support for log4j2 in HiveMain https://issues.apache.org/jira/browse/OOZIE-3137 OOZIE-3135 Configure log4j2 in SqoopMain https://issues.apache.org/jira/browse/OOZIE-3135 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-2952 Fix Findbugs warnings in oozie-sharelib-oozie https://issues.apache.org/jira/browse/OOZIE-2952 OOZIE-2927 Append new line character for Hive2 query using query tag https://issues.apache.org/jira/browse/OOZIE-2927 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-2812 SparkConfigurationService should support loading configurations from multiple Spark versions https://issues.apache.org/jira/browse/OOZIE-2812 OOZIE-2795 Create lib directory or symlink for Oozie CLI during packaging https://issues.apache.org/jira/browse/OOZIE-2795 OOZIE-2784 Include WEEK as a parameter in the Coordinator Expression Language Evaulator https://issues.apache.org/jira/browse/OOZIE-2784 OOZIE-2779 Mask Hive2 action Beeline JDBC password
