[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17643201#comment-17643201 ] Janos Makai commented on OOZIE-3606: Thank you [~dionusos] > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Janos Makai >Priority: Major > Fix For: 5.3.0 > > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch, > OOZIE-3606-003.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642045#comment-17642045 ] ASF subversion and git services commented on OOZIE-3606: Commit 4f4e9ee43daf2c8e86b56cabf674a3a4e606007f in oozie's branch refs/heads/master from Denes Bodo [ https://gitbox.apache.org/repos/asf?p=oozie.git;h=4f4e9ee43 ] OOZIE-3606 Extend file system EL functions to use custom file system properties (jmakai via dionusos) > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch, > OOZIE-3606-003.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641847#comment-17641847 ] Janos Makai commented on OOZIE-3606: Hello [~dionusos], could you please review the latest patch? I've checked the SpotBugs results, and the issues are unrelated to this change. > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch, > OOZIE-3606-003.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[
https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641483#comment-17641483
]
Hadoop QA commented on OOZIE-3606:
--
Testing JIRA OOZIE-3606
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 star imports
.{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} 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 [20] 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
[fluent-job/fluent-job-api].
.{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/distcp].
.{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/spark].
.{color:red}-1{color} There are [1] new bugs found below threshold in
[sharelib/oozie] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
sharelib/oozie/findbugs-new.html
.The most important SpotBugs errors are:
.At ShellMain.java:[line 93]: This usage of
java/lang/ProcessBuilder.(Ljava/util/List;)V can be vulnerable to
Command Injection
.At ShellMain.java:[line 91]: At ShellMain.java:[line 90]
.At ShellMain.java:[line 92]
.{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: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{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [webapp].
.{color:red}-1{color} There are [4] new bugs found below threshold in
[core] that must be fixed.
.You can find the SpotBugs diff here (look for the red and orange ones):
core/findbugs-new.html
.The most important SpotBugs errors are:
.At BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.java/io/File.(Ljava/lang/String;Ljava/lang/String;)V reads a
file whose location might be specified by user input: At
BulkJPAExecutor.java:[line 206]
.At AuthorizationService.java:[line 189]: At
AuthorizationService.java:[line 192]
.{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 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [client].
{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}
.T
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641431#comment-17641431 ] Hadoop QA commented on OOZIE-3606: -- PreCommit-OOZIE-Build started > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Janos Makai >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch, > OOZIE-3606-003.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631584#comment-17631584 ] Dénes Bodó commented on OOZIE-3606: --- Hey [~jmakai] Sorry for abandoning this. I can continue the work on this but I am not sure when exactly. If you need this change soon then feel free to finish it or do changes accordingly. If you need, just use my patch as a starting point or implement a different approach. It is up to you. Thanks > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Dénes Bodó >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17631567#comment-17631567 ] Janos Makai commented on OOZIE-3606: [~dionusos] are you planning to continue the work on this? > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Dénes Bodó >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[
https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186831#comment-17186831
]
Hadoop QA commented on OOZIE-3606:
--
Testing JIRA OOZIE-3606
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 star imports
.{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} 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 [21] 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 [6] 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 BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{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/git].
.{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/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/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/hcatalog].
.{color:green}+1{color} There are no new bugs found in [sharelib/distcp].
.{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 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{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 [examples].
.{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:green}+1 TESTS{color}
.Tests run: 3218
.{color:orange}Tests failed at first run:{color}
TestPriorityDelayQueue#testPeek
.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:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is available at
. https://ci-hado
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186802#comment-17186802 ] Hadoop QA commented on OOZIE-3606: -- PreCommit-OOZIE-Build started > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Dénes Bodó >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[
https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17167083#comment-17167083
]
Hadoop QA commented on OOZIE-3606:
--
Testing JIRA OOZIE-3606
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 star imports
.{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} 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 [21] new bugs found below threshold in total
that must be fixed.
.{color:green}+1{color} There are no new bugs found in [webapp].
.{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 [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/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/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 [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/hive2].
.{color:green}+1{color} There are no new bugs found in [sharelib/oozie].
.{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 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{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{color} There are no new bugs found in [examples].
.{color:green}+1{color} There are no new bugs found in [docs].
.{color:green}+1{color} There are no new bugs found in [client].
.{color:red}-1{color} There are [6] 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 BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
{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: 3218
.Tests failed : 0
.Tests in error : 3
.Tests timed out : 0
{color:red}-1{color} [ERROR] There are [3] test errors in [tools]. Listing only
the first [5] ones
testConcurrentCopyFromLocalHighThreadNr:org.apache.oozie.tools.TestConcurrentCopyFromLocal
testConcurrentCopyFromLocalSameFileNrAndThreadNr:org.apache.oozie.tools.TestConcurre
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166938#comment-17166938 ] Hadoop QA commented on OOZIE-3606: -- PreCommit-OOZIE-Build started > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Dénes Bodó >Priority: Major > Attachments: OOZIE-3606-001.patch, OOZIE-3606-002.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[
https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166274#comment-17166274
]
Hadoop QA commented on OOZIE-3606:
--
Testing JIRA OOZIE-3606
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:red}-1{color} the patch contains 2 line(s) with trailing spaces
.{color:green}+1{color} the patch does not introduce any star imports
.{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} 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 [21] 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
[fluent-job/fluent-job-api].
.{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/distcp].
.{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/spark].
.{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/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 [server].
.{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:red}-1{color} There are [6] 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 BulkJPAExecutor.java:[line 206]: This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection
.At BulkJPAExecutor.java:[line 176]: At BulkJPAExecutor.java:[line 175]
.At BulkJPAExecutor.java:[line 205]: At BulkJPAExecutor.java:[line 199]
.This use of
javax/persistence/EntityManager.createQuery(Ljava/lang/String;)Ljavax/persistence/Query;
can be vulnerable to SQL/JPQL injection: At BulkJPAExecutor.java:[line 206]
.At BulkJPAExecutor.java:[line 111]: At BulkJPAExecutor.java:[line 127]
.{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 584]: This use of
java/sql/Statement.executeUpdate(Ljava/lang/String;)I can be vulnerable to SQL
injection
.At OozieDBCLI.java:[line 574]: At OozieDBCLI.java:[line 573]
.At OozieDBCLI.java:[line 577]: At OozieDBCLI.java:[line 575]
.At OozieDBCLI.java:[line 579]: At OozieDBCLI.java:[line 578]
.At OozieDBCLI.java:[line 584]: At OozieDBCLI.java:[line 581]
.{color:green}+1{color} There are no new bugs found in [client].
{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: 3218
.{color:orange}Tests failed at first run:{color}
TestBlockingInputStream#testFastWritingBlockingInputStream
.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:green}+1 MODERNIZER{color}
{color:red}*-1 Overall result, please check the reported -1(s)*{color}
The full output of the test-patch run is availab
[jira] [Commented] (OOZIE-3606) Extend file system EL functions to use custom file system properties
[ https://issues.apache.org/jira/browse/OOZIE-3606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17166198#comment-17166198 ] Hadoop QA commented on OOZIE-3606: -- PreCommit-OOZIE-Build started > Extend file system EL functions to use custom file system properties > > > Key: OOZIE-3606 > URL: https://issues.apache.org/jira/browse/OOZIE-3606 > Project: Oozie > Issue Type: Improvement > Components: core >Affects Versions: 5.2.0 >Reporter: Dénes Bodó >Assignee: Dénes Bodó >Priority: Major > Attachments: OOZIE-3606-001.patch > > > In case we want to check file availability on abfss file system in scope of a > decision node and we have access to that file system only using a key file > which is password protected then currently we are blocked as we cannot allow > configuring hadoop.security.credstore.java-keystore-provider.password-file > globally. > This is why this ticket is created to propose a solution for this issue: > * allow special file system configurations only for file system EL functions > * let them configure globally via oozie-site.xml and for every workflow > independently -- This message was sent by Atlassian Jira (v8.3.4#803005)
