[jira] [Resolved] (HIVE-29046) Avoid unecessary perf overhead from handling deprecated properties in MetastoreConf

["Stamatis Zampetakis (Jira)" <ji...@apache.org>]

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

Stamatis Zampetakis resolved HIVE-29046.
----------------------------------------
    Fix Version/s: 4.2.0
       Resolution: Fixed

Fixed in https://github.com/apache/hive/commit/171340ad38ee8d082f6992a416c5aad63377d708

> Avoid unecessary perf overhead from handling deprecated properties in MetastoreConf
> -----------------------------------------------------------------------------------
>
>                 Key: HIVE-29046
>                 URL: https://issues.apache.org/jira/browse/HIVE-29046
>             Project: Hive
>          Issue Type: Improvement
>          Components: Standalone Metastore
>            Reporter: Stamatis Zampetakis
>            Assignee: Stamatis Zampetakis
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.2.0
>
>
> Currently, on every creation of a new MetastoreConf instance we are [looping through ~400 ConfVars|https://github.com/apache/hive/blob/90b48ff2fe68e14ebdd02ca718814114384f99e5/standalone-metastore/metastore-common/src/main/java/org/apache/hadoop/hive/metastore/conf/MetastoreConf.java#L2249] enumeration entries to detect and register deprecated properties.
> The deprecated properties are static and known at compile time so there is no reason to search and register them on every creation of a new Configuration instance. The current logic is resource wasteful and unnecessary. In addition, the presence of deprecation information inside the ConfVars enumeration leads to boilerplate code that is not really necessary.
> The deprecation logic can be moved in a static block and the all the code for the bookeeping deprecated properties in ConfVars can be dropped.



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