[
https://issues.apache.org/jira/browse/IMPALA-7054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16482829#comment-16482829
]
Philip Zeyliger commented on IMPALA-7054:
-----------------------------------------
Is this a dupe of:
{code:java}
commit ea4715fd76d6dba0c3777146989c2bf020efabdd
Author: stiga-huang <[email protected]>
Date: Thu May 3 06:44:42 2018 -0700
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]>{code}
> "Top-25 tables with highest memory requirements" sorts incorrectly
> ------------------------------------------------------------------
>
> Key: IMPALA-7054
> URL: https://issues.apache.org/jira/browse/IMPALA-7054
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.12.0
> Reporter: Todd Lipcon
> Priority: Minor
>
> The table on catalogd:25020/catalog has an "estimated memory" column which
> sorts based on the stringified value. For example, "2.07 GB" sorts below
> "23.65 MB".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
