[ https://issues.apache.org/jira/browse/AMBARI-21232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16216003#comment-16216003 ]
Swapan Shridhar commented on AMBARI-21232: ------------------------------------------ [~mradhakrishnan] Can you check on this ? if its not committed, please move it to 2.6.1 and take action on it, as required. > Determination of defaultFS with WebHDFS enabled > ----------------------------------------------- > > Key: AMBARI-21232 > URL: https://issues.apache.org/jira/browse/AMBARI-21232 > Project: Ambari > Issue Type: Improvement > Components: ambari-views > Affects Versions: 2.4.0 > Reporter: Sridhar Sailappan > Assignee: Madhuvanthi Radhakrishnan > Fix For: 2.6.0 > > Attachments: Patch_AmbariViewUtils_WebHDFS.txt > > > In Ambari View Utils , the determination logic for the value of defaultFS > when WebHDFS is enabled, needs to consider the current property value of > defaultFS. Please see attached patch for the context. > If the existing configuration for the defaultFS URI already has the protocol > specified as webhdfs or swebhdfs, the URI should be used as provided and a > new value should not be constructed. Constructing a new value in a such a > scenario may lead to unexpected behavior if the Namenode has different > host-port settings for the HTTP and WebHDFS access. > The patch also addresses the following code cleanup: > 1) Fix variable names httpAddr and httpsAddr (current implementation has > the naming interchanged) > 2) Add null value check for httpAddr before assignment to hostWithPort > 3) Fix typo in variable names - DFS_NAMENODE_HTTP_ADDRESS and > DFS_NAMENODE_HTTPS_ADDRESS -- This message was sent by Atlassian JIRA (v6.4.14#64029)