[
https://issues.apache.org/jira/browse/IMPALA-6966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504953#comment-16504953
]
ASF subversion and git services commented on IMPALA-6966:
---------------------------------------------------------
Commit 0a3413ec5f4b6b44c3dff74facf4133b5144d319 in impala's branch
refs/heads/2.x from stiga-huang
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=0a3413e ]
IMPALA-7082: Show human readable size in query backend page
This patch reuse the JS function introduced in IMPALA-6966,
which can convert Long size value into human readable size,
to render the "Peak mem. consumption" column in the Query
details's Backends page.
Change-Id: I04afb4091bb8b6bc9dedfeceaf9284a8c65b16a1
Reviewed-on: http://gerrit.cloudera.org:8080/10523
Reviewed-by: Philip Zeyliger <[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
> Fix For: Impala 2.13.0, Impala 3.1.0
>
> 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]
