[jira] [Created] (HIVE-29330) HiveMetaStoreAuthorizer creating new HiveConf per thread increases overhead

["Zhihua Deng (Jira)" <ji...@apache.org>]

Zhihua Deng created HIVE-29330:
----------------------------------

             Summary: HiveMetaStoreAuthorizer creating new HiveConf per thread increases overhead
                 Key: HIVE-29330
                 URL: https://issues.apache.org/jira/browse/HIVE-29330
             Project: Hive
          Issue Type: Improvement
            Reporter: Zhihua Deng


HiveMetaStoreAuthorizer can act as a pre event listener inside the HMS, or as the metadata filter hook on the client. If it's insides the HMS, getConf() should have loaded all properties in hive-site.xml, otherwise it contains the information to talk with the HMS at least, as the call is from client as a filter hook.

We don't need to create a new HiveConf per thread, it's wasteful and might spend dozens of milliseconds to load the properties, log the warn message "HiveConf of name xx does not exist" continuously if the property is only specified in MetastoreConf.



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