[
https://issues.apache.org/jira/browse/IMPALA-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong resolved IMPALA-661.
----------------------------------
Resolution: Later
Closing some JIRAs that have useful suggestions but limited interest. We can
reopen if there is more interest.
> Explain plan should characterize the cost of evaluating predicates
> ------------------------------------------------------------------
>
> Key: IMPALA-661
> URL: https://issues.apache.org/jira/browse/IMPALA-661
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Affects Versions: Impala 1.1.1, Impala 2.5.0
> Reporter: Alan Choi
> Priority: Minor
>
> Explain plan is an effective tool for tuning query. However, it doesn't give
> much inside into the (cpu) cost of expression evaluation. For complex
> predicates, it'll greatly affect the runtime of the query. For example,
> complex regex is very costly to evaluate.
> Right now, if a complex join predicate cause the join to slow down, it's not
> very easy to tell.
> If explain plan can annotate the cost of predicate evaluation (roughly), then
> it can guide our user to identify and tune the predicates.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
