[jira] [Commented] (HADOOP-18993) Allow to not isolate S3AFileSystem classloader when needed

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HADOOP-18993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791931#comment-17791931 ] 

ASF GitHub Bot commented on HADOOP-18993:
-----------------------------------------

tmnd1991 commented on PR #6301:
URL: https://github.com/apache/hadoop/pull/6301#issuecomment-1835627559

   Hi @steveloughran , can you have a look at the PR?
   P.S. I don't know how CI/CD of Hadoop works, but I see a checkstyle failed for a file that is not (anymore) part of the changes. Is this normal? How can I fix it?




> Allow to not isolate S3AFileSystem classloader when needed
> ----------------------------------------------------------
>
>                 Key: HADOOP-18993
>                 URL: https://issues.apache.org/jira/browse/HADOOP-18993
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: hadoop-thirdparty
>    Affects Versions: 3.3.6
>            Reporter: Antonio Murgia
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 3.4.0
>
>
> In HADOOP-17372 the S3AFileSystem forces the configuration classloader to be the same as the one that loaded S3AFileSystem. This leads to the impossibility in Spark applications to load third party credentials providers as user jars.
> I propose to add a configuration key {{fs.s3a.extensions.isolated.classloader}} with a default value of {{true}} that if set to {{false}} will not perform the classloader set.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org