[
https://issues.apache.org/jira/browse/IMPALA-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-1694.
-----------------------------------
Resolution: Later
> Improve logging in the catalog
> ------------------------------
>
> Key: IMPALA-1694
> URL: https://issues.apache.org/jira/browse/IMPALA-1694
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 2.1
> Reporter: Dimitris Tsirogiannis
> Priority: Major
> Labels: catalog-server, impala
>
> The existing logging in the catalog is not always very useful when trying to
> resolve catalog issues, especially due to concurrent operations. We should
> modify logging in the catalog to:
> 1. Record all high level operations (e.g. DDL statements, reset
> metadata/refresh stmts, etc) that are executed in the catalog.
> 2. Remove "spurious" logging statements that aren't very useful or assign
> them to higher logging levels (trace).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)