[
https://issues.apache.org/jira/browse/HDFS-5312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13850960#comment-13850960
]
Hudson commented on HDFS-5312:
------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #4903 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/4903/])
Move HDFS-5538, HDFS-5545, HDFS-5536, HDFS-5312, and HDFS-5629 from trunk to
2.4.0 section. (jing9:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1551724)
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
> Generate HTTP / HTTPS URL in DFSUtil#getInfoServer() based on the configured
> http policy
> ----------------------------------------------------------------------------------------
>
> Key: HDFS-5312
> URL: https://issues.apache.org/jira/browse/HDFS-5312
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Haohui Mai
> Assignee: Haohui Mai
> Fix For: 2.4.0
>
> Attachments: HDFS-5312.000.patch, HDFS-5312.001.patch,
> HDFS-5312.002.patch, HDFS-5312.003.patch, HDFS-5312.004.patch,
> HDFS-5312.005.patch, HDFS-5312.006.patch, HDFS-5312.007.patch,
> HDFS-5312.008.patch
>
>
> DFSUtil#getInfoServer() returns only the authority (i.e., host+port) when
> searching for the http / https server. This is insufficient because HDFS-5536
> and related jiras allows NN / DN / JN to open HTTPS only using the HTTPS_ONLY
> policy.
> This JIRA addresses two issues. First, DFSUtil#getInfoServer() should return
> an URI instead of a string, so that the scheme is an inherent parts of the
> return value, which eliminates the task of figuring out the scheme by design.
> Second, it introduces a new function to choose whether http or https should
> be used to connect to the remote server based of dfs.http.policy.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
