[jira] [Commented] (IMPALA-7527) Expose fetch-from-catalogd cache and latency metrics in profiles

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-7527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635862#comment-16635862 ] 

ASF subversion and git services commented on IMPALA-7527:
---------------------------------------------------------

Commit ea2809f5ddcf48f3f41dcd12743e8a17b4ea8cd7 in impala's branch refs/heads/master from [~vercego]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=ea2809f ]

Revert "IMPALA-7527: add fetch-from-catalogd cache info to profile"

Update to profile conflicts with downstream dependency (change 2/2).

This reverts commit 8c330adf409aa74857b23ba345f0c710a1f25a32.

Change-Id: Ide56f2cd3ee6a34f716b6b465f6fb5fb944e7db8
Reviewed-on: http://gerrit.cloudera.org:8080/11560
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>


> Expose fetch-from-catalogd cache and latency metrics in profiles
> ----------------------------------------------------------------
>
>                 Key: IMPALA-7527
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7527
>             Project: IMPALA
>          Issue Type: Sub-task
>    Affects Versions: Impala 3.1.0
>            Reporter: Todd Lipcon
>            Assignee: Vuk Ercegovac
>            Priority: Major
>             Fix For: Impala 3.1.0
>
>
> Since we now have some caching and potential remote calls on the planning path, it's important to be able to understand how that contributes to the performance of planning. This JIRA tracks adding such information to the profile.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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