[
https://issues.apache.org/jira/browse/KNOX-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16703684#comment-16703684
]
Kevin Risden commented on KNOX-1644:
------------------------------------
The host= is only in 3.0.0. I checked and 2.7.0 doesn't have host= handling.
The 3.0.0 change broke expectations for people upgrading Knox (existing url
with /hdfs/ do not work now) and the documentation is out of date for this now:
https://knox.apache.org/books/knox-1-1-0/user-guide.html#Name+Node+UI+URL+Mapping
The above examples do not work and return a 500 error.
There are other examples where no namenode is specified:
*
https://community.hortonworks.com/articles/81713/configure-knox-to-access-hdfs-ui.html
The other surprise to me is that this requires the user to know the HDFS
namenode hostnames (and ports). Before it was semi transparent and could look
at the status of HDFS without knowing the namenode hosts.
> Remove HDFSUI 3.0.0 version
> ---------------------------
>
> Key: KNOX-1644
> URL: https://issues.apache.org/jira/browse/KNOX-1644
> Project: Apache Knox
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: Kevin Risden
> Assignee: Kevin Risden
> Priority: Blocker
> Fix For: 1.2.0
>
> Attachments: KNOX-1644.patch
>
>
> Currently the HDFSUI service is broken with version 3.0.0. Version 2.7.0
> works. It looks like there were a bunch of changes to the 2.7.0 version but
> not the 3.0.0 version. Version 2.7.0 seems to fix the issue that 3.0.0 was
> introduced for. We should remove it since currently version 3.0.0 is broken.
> Version 3.0.0 was introduced in KNOX-1340
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
