[jira] [Commented] (IMPALA-9903) Queries on a Kudu table call openTable multiple times

["Tim Armstrong (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IMPALA-9903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147958#comment-17147958 ] 

Tim Armstrong commented on IMPALA-9903:
---------------------------------------

[~granthenke] do you know if this was with --use_local_catalog=true? Was this a select query? We could definitely optimise this if we just ensure it's cached for the duration of the query.


> 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-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org