[
https://issues.apache.org/jira/browse/IMPALA-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aman Sinha closed IMPALA-500.
-----------------------------
Resolution: Won't Fix
We haven't seen a compelling need for creating hash of the query text or the
plan and considering this JIRA is quite old, closing this for now. I think that
if and when we add plan caching (for parameterized queries to re-use the same
plan), it would make sense to revisit something like this.
> implment query hashes and query plan hashes
> -------------------------------------------
>
> Key: IMPALA-500
> URL: https://issues.apache.org/jira/browse/IMPALA-500
> Project: IMPALA
> Issue Type: New Feature
> Components: Frontend
> Affects Versions: Impala 1.1
> Reporter: Greg Rahn
> Priority: Minor
>
> Having hashes for the query text and the query execution plan in the log (and
> other places) would make comparing plans or finding identical queries easier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
