[
https://issues.apache.org/jira/browse/HADOOP-12279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644967#comment-14644967
]
Steve Loughran commented on HADOOP-12279:
-----------------------------------------
You can't fix the endpoint in Hadoop s3n, see HADOOP-9248. That option is only
there —and documented as such— for the successor filesystem client, s3a.
That's OK though, as you can just set it in the URL. This is precisely how
vendors of S3-compatible object stores test with the s3n.
Closing as a duplicate of HADOOP-9248
> Setting Enpoint for hadoop-aws s3n doesn't work
> -----------------------------------------------
>
> Key: HADOOP-12279
> URL: https://issues.apache.org/jira/browse/HADOOP-12279
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/s3
> Affects Versions: 2.6.0
> Reporter: schmirr
>
> I tried to access a S3 compatible storage from spark/zeppelin.
> I wasn't able to get another endpoint working :
> sc.hadoopConfiguration.set("s3service.s3-endpoint","test")
> sc.hadoopConfiguration.set("fs.s3n.endpoint","test")
> sc.hadoopConfiguration.set("fs.s3n.s3-endpoint","test")
> All the 3 are working, and giving me a file back from amazon, even with
> "test" as endpoint...
> I'm using org.apache.hadoop:hadoop-aws:2.6.0
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
