[jira] [Updated] (IMPALA-7551) Inaccurate timeline for "Row Available"
[ https://issues.apache.org/jira/browse/IMPALA-7551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Armstrong updated IMPALA-7551: -- Labels: query-lifecycle (was: ) > Inaccurate timeline for "Row 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: query-lifecycle > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7551) Inaccurate timeline for "Row Available"
[ https://issues.apache.org/jira/browse/IMPALA-7551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker updated IMPALA-7551: Component/s: Backend > Inaccurate timeline for "Row 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 > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
[jira] [Updated] (IMPALA-7551) Inaccurate timeline for "Row Available"
[ https://issues.apache.org/jira/browse/IMPALA-7551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lars Volker updated IMPALA-7551: Affects Version/s: Impala 3.1.0 > Inaccurate timeline for "Row 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 > > 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. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org For additional commands, e-mail: issues-all-h...@impala.apache.org
