Noemi Pap-Takacs created IMPALA-13616:
-----------------------------------------
Summary: Catalog timeline is missing from query profile in case of
exception
Key: IMPALA-13616
URL: https://issues.apache.org/jira/browse/IMPALA-13616
Project: IMPALA
Issue Type: Improvement
Components: Catalog
Reporter: Noemi Pap-Takacs
The query profile contains a timeline for Catalog, Query Compilation and 'Query
Timeline' under 'Errors'.
This is an example of a successful DML operation.
{noformat}
Errors:
Catalog Server Operation: 533.758ms
- Got catalog version read lock: 2.746ms (2.746ms)
- Got catalog version write lock and table write lock: 2.870ms
(124.249us)
- Executed Iceberg operation OPTIMIZE: 243.529ms (240.658ms)
- Updated table properties: 248.339ms (4.810ms)
- Got Metastore client: 470.222ms (221.882ms)
(...)
- Finished updateCatalog request: 533.758ms (428.717us)
Query Compilation: 4s832ms
- Metadata load started: 525.705us (525.705us)
(..)
- Distributed plan created: 4s617ms (11.530ms)
- Planning finished: 4s832ms (215.162ms)
Query Timeline: 7s653ms
- Query submitted: 44.775us (44.775us)
- Planning finished: 4s846ms (4s846ms)
(..)
- Request finished: 7s609ms (1.188us)
- Unregister query: 7s653ms (43.672ms)
- AdmissionControlTimeSinceLastUpdate: 86.000ms
- ComputeScanRangeAssignmentTimer: 34.764us
{noformat}
However, if a runtime exception occurs, for example a ValidationException is
thrown from Iceberg, the Catalog timeline disappears from the profile:
{noformat}
Errors:
Query Compilation: 5s361ms
- Metadata load started: 5.080ms (5.080ms)
(...)
{noformat}
We should include the Catalog timeline in this case as well in order to gain
observability.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
