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 "Balazs Jeszenszky (Jira)" <ji...@apache.org> on 2021/10/14 11:33:00 UTC

[jira] [Assigned] (IMPALA-6665) Tag CatalogOp logs with query IDs

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

Balazs Jeszenszky reassigned IMPALA-6665:
-----------------------------------------

    Assignee:     (was: Balazs Jeszenszky)

> Tag CatalogOp logs with query IDs
> ---------------------------------
>
>                 Key: IMPALA-6665
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6665
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Catalog
>    Affects Versions: Impala 2.12.0
>            Reporter: Bharath Vissapragada
>            Priority: Major
>              Labels: supportability
>
> Similar to IMPALA-6664. The idea is to improve catalog server logging by adding query-ID to each of the Catalog server log statements. This helps map Catalog errors to specific queries, which is currently not possible. 
> Raising a separate jira for the Catalog server since fixing it could be a little tricker than the other components since we don't have the query hash readily available in the Catalog context. We need to augment the Catalog RPCs with this data. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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