You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2023/04/10 03:02:00 UTC

[jira] [Updated] (HIVE-27238) Avoid Calcite Code generation for RelMetaDataProvider on every query

     [ https://issues.apache.org/jira/browse/HIVE-27238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HIVE-27238:
----------------------------------
    Labels: pull-request-available  (was: )

> Avoid Calcite Code generation for RelMetaDataProvider on every query
> --------------------------------------------------------------------
>
>                 Key: HIVE-27238
>                 URL: https://issues.apache.org/jira/browse/HIVE-27238
>             Project: Hive
>          Issue Type: Improvement
>          Components: HiveServer2
>            Reporter: Steve Carlin
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In CalcitePlanner, we are instantiating a new CachingRelMetadataProvider on every query.  Within the Calcite code, they keep the provider key to prevent a new MetadataHandler class from being created.  But by generating a new provider, the cache never gets a hit so we keep instantiating new MetadataHandlers.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)