You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2025/06/03 21:56:00 UTC

[jira] [Assigned] (IMPALA-13945) Change the tuple cache key trace to display an individual node's contribution

     [ https://issues.apache.org/jira/browse/IMPALA-13945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joe McDonnell reassigned IMPALA-13945:
--------------------------------------

    Assignee: Joe McDonnell

> Change the tuple cache key trace to display an individual node's contribution
> -----------------------------------------------------------------------------
>
>                 Key: IMPALA-13945
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13945
>             Project: IMPALA
>          Issue Type: Task
>          Components: Frontend
>    Affects Versions: Impala 5.0.0
>            Reporter: Joe McDonnell
>            Assignee: Joe McDonnell
>            Priority: Major
>
> As tuple caching is supported higher in the plan tree, the cache key trace can become enormous, as it includes all of its childrens' information plus its own contribution. An individual trace can take up over a hundred lines in the profile. It can be hard to determine which contribution comes from which child.
> We should break up the hash trace and display each node's individual contribution to the hash trace. This should be smaller in the profile and more clearer display what is new at each level.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org