[
https://issues.apache.org/jira/browse/HDFS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16164910#comment-16164910
]
Kihwal Lee edited comment on HDFS-12424 at 9/13/17 4:27 PM:
------------------------------------------------------------
Reattaching the patch to kick the trunk precommit build. Unfortunately the 2.8
patch naming caused to build branch-2.8.1, which still tried to download jdk7
from Oracle. It should be named to not match other existing branch
unintentionally. In any case, the build does not build or test the UI change.
was (Author: kihwal):
Reattaching the patch to kick the trunk precommit build. Unfortunately the 2.8
patch naming caused to build branch-2.8.1, which still tried to download jdk7
from Oracle. It should be name to not match other existing branch. In any
case, the build does not build or test the UI change.
> Datatable sorting on the Datanode Information page in the Namenode UI is
> broken
> -------------------------------------------------------------------------------
>
> Key: HDFS-12424
> URL: https://issues.apache.org/jira/browse/HDFS-12424
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 2.8.1
> Reporter: Shawna Martell
> Assignee: Shawna Martell
> Attachments: HDFS-12424.1.patch, HDFS-12424.1.patch,
> HDFS-12424-branch-2.8.1.patch
>
>
> Attempting to sort the "In operation" table by Last contact, Capacity,
> Blocks, or Version can result in unexpected behavior. Sorting by Blocks and
> Version actually sort by entirely different columns, and Last contact and
> Capacity are not being sorted numerically but rather alphabetically.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
