[
https://issues.apache.org/jira/browse/HADOOP-18295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17555718#comment-17555718
]
Steve Loughran commented on HADOOP-18295:
-----------------------------------------
You can do this today on a per Bucket basis just by setting the proxy host to
an empty string.
Now there is a little detail here which relates to configurations and
overrides, it may be better to put one or more spaces in there rather than a
completely empty element.
Either way, this works today. You can set a global proxy setting and then
disable it for those those you have inside of the firewall.
Try it!
I'm not sure what adding a new option would be except extra complication in
testing and documentation. In particular, do you have to handle the situation
where a bucket has been given an explicit proxy and it is also listed in the no
proxy option
> Add S3A configuration property for `no_proxy` hosts
> ---------------------------------------------------
>
> Key: HADOOP-18295
> URL: https://issues.apache.org/jira/browse/HADOOP-18295
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs/s3
> Reporter: Sam Kramer
> Priority: Minor
>
> Seeing as there are configuration options for proxy host, port, username, and
> password, there should also be an option to be able to provide to the S3
> client a list of hosts to not use the proxy for (i.e. `no_proxy`)
>
> I'm happy to contribute the code, but figured I'd file a ticket first to see
> if this the hadoop community would be open to this idea or have any desire
> for this feature.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
