[
https://issues.apache.org/jira/browse/IMPALA-7507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18010546#comment-18010546
]
Quanlong Huang commented on IMPALA-7507:
----------------------------------------
We should also improve the logs of "Check the catalog server log for more
details" to show the actual time that table loading failed.
[https://github.com/apache/impala/blob/5af4fa84df68c647b9dc6c2635228ece2eee044d/fe/src/main/java/org/apache/impala/catalog/ParallelFileMetadataLoader.java#L216-L217]
Such exceptions are stored in the IncompleteTable and reported everytime users
try to use a failed loaded table. The metadata loading logs containing the
actual failure might be days ago.
[https://github.com/apache/impala/blob/5af4fa84df68c647b9dc6c2635228ece2eee044d/fe/src/main/java/org/apache/impala/catalog/IncompleteTable.java#L67]
> Clean up user-facing error messages in LocalCatalog mode
> --------------------------------------------------------
>
> Key: IMPALA-7507
> URL: https://issues.apache.org/jira/browse/IMPALA-7507
> Project: IMPALA
> Issue Type: Sub-task
> Components: Catalog
> Affects Versions: Impala 3.1.0
> Reporter: Todd Lipcon
> Assignee: Quanlong Huang
> Priority: Major
> Labels: catalog-v2
>
> Currently even normal error messages for things like missing databases are
> quite ugly when running with LocalCatalog:
> {code}
> ERROR: LocalCatalogException: Could not load table names for database
> 'test_minimal_topic_updates_b246004e' from HMS
> CAUSED BY: TException:
> TGetPartialCatalogObjectResponse(status:TStatus(status_code:GENERAL,
> error_msgs:[CatalogException: Database not found:
> test_minimal_topic_updates_b246004e]))
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
