You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Hadoop QA (Jira)" <ji...@apache.org> on 2020/08/28 20:28:00 UTC

[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)