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