[
https://issues.apache.org/jira/browse/IMPALA-12473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17770200#comment-17770200
]
Surya Hebbar commented on IMPALA-12473:
---------------------------------------
!q4_json_profile_missing_event_timestamp.png!
In this JSON profile, the event "Closed" (and its timestamp) is not
encountered in one of the child node's event sequences, but it should have been
present. Hence in this example, at the end, there are 288 timestamps
accumulated for other events, but for the "Closed" event, only 287 timestamps
can be collected.
> Fix query profile's missing event timestamps exception in query timeline
> ------------------------------------------------------------------------
>
> Key: IMPALA-12473
> URL: https://issues.apache.org/jira/browse/IMPALA-12473
> Project: IMPALA
> Issue Type: Bug
> Reporter: Surya Hebbar
> Assignee: Surya Hebbar
> Priority: Minor
> Attachments: q4_json_profile_missing_event_timestamp.png,
> q64_json_profile_missing_event_timestamp.png
>
>
> The query profile contains different fragment's and there plan node's event
> timestamps.
>
> Sometimes the expected timestamps from an event are missing, this currently
> throws an exception, hence it stops the rendering of query timeline.
>
> The issue needs to be fixed with some validation of these timestamp event
> labels, without raising an exception.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
