[
https://issues.apache.org/jira/browse/IMPALA-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148000#comment-17148000
]
Grant Henke edited comment on IMPALA-9903 at 6/29/20, 5:23 PM:
---------------------------------------------------------------
These were select queries, and those are the queries I am most concerned about
given their frequency. Other queries aren't as critical.
This was with `--use_local_catalog=true`.
Caching for the duration of the query is exactly what I was thinking.
was (Author: granthenke):
These were select queries, and those are the queries I am most concerned about
given their frequency. Other queries aren't as critical.
I don't think this was with `--use_local_catalog=true`.
Caching for the duration of the query is exactly what I was thinking.
> Queries on a Kudu table call openTable multiple times
> -----------------------------------------------------
>
> Key: IMPALA-9903
> URL: https://issues.apache.org/jira/browse/IMPALA-9903
> Project: IMPALA
> Issue Type: Improvement
> Components: Frontend
> Affects Versions: Impala 3.4.0
> Reporter: Grant Henke
> Priority: Major
> Labels: kudu, performance
>
> When testing the results of KUDU-1802 I saw that each query ran would result
> in 5 GetTableSchema requests to the Kudu master server. The request comes
> from each KuduClient.openTable call in the Impala frontend.
> https://github.com/apache/impala/search?l=Java&q=openTable
> Ideally Impala would only call KuduClient.openTable once and then use the
> returned KuduTable object for the length of the query. That would result in
> 5x fewer remote RPC calls to the Kudu master server per query.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
