[
https://issues.apache.org/jira/browse/IMPALA-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16471333#comment-16471333
]
ASF subversion and git services commented on IMPALA-6966:
---------------------------------------------------------
Commit ea4715fd76d6dba0c3777146989c2bf020efabdd in impala's branch
refs/heads/master from stiga-huang
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=ea4715f ]
IMPALA-6966: sort table memory by size in catalogd web UI
This patch fix the sorting order in "Top-K Tables with Highest
Memory Requirements" in which "Estimated memory" column is sorted
as strings.
Values got from the catalog-server are changed from pretty-printed
strings to bytes numbers. So the web UI is able to sort and render
them correctly.
Change-Id: I60dc253f862f5fde6fa96147f114d8765bb31a85
Reviewed-on: http://gerrit.cloudera.org:8080/10292
Reviewed-by: Dimitris Tsirogiannis <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Estimated Memory in Catalogd webpage is not sorted correctly
> ------------------------------------------------------------
>
> Key: IMPALA-6966
> URL: https://issues.apache.org/jira/browse/IMPALA-6966
> Project: IMPALA
> Issue Type: Bug
> Affects Versions: Impala 3.0, Impala 2.12.0
> Reporter: Quanlong Huang
> Assignee: Quanlong Huang
> Priority: Major
> Labels: newbie
> Attachments: Screen Shot 2018-05-03 at 9.38.45 PM.png
>
>
> The "Top-N Tables with Highest Memory Requirements" in Catalogd webpage
> doesn't sort "Estimated Memory" correctly. In fact, it sorts them as strings
> instead of size. This is confusing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
