[
https://issues.apache.org/jira/browse/IMPALA-7551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Volker updated IMPALA-7551:
--------------------------------
Labels: observability query-lifecycle ramp-up (was: observability
query-lifecycle)
> Inaccurate timeline for "Rows Available"
> -----------------------------------------
>
> Key: IMPALA-7551
> URL: https://issues.apache.org/jira/browse/IMPALA-7551
> Project: IMPALA
> Issue Type: Improvement
> Components: Backend
> Affects Versions: Impala 3.1.0
> Reporter: Pooja Nilangekar
> Priority: Major
> Labels: observability, query-lifecycle, ramp-up
>
> While debugging IMPALA-6932, it was noticed that the "Rows Available" metric
> in the query profile was a short duration (~ 1 second) for a long running
> limit 1 query (~ 1 hour).
> Currently, it tracks when Open() from the top-most node in the plan returns,
> not when the first row is actually produced. This can be misleading. A better
> timeline would be to return true when the first non-empty batch was added to
> the PlanRootSink.
> We should consider changing the definition of the FINISHED state accordingly
> as well, so that we don't transition to FINISHED until a row is actually
> available to fetch immediately.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
