[
https://issues.apache.org/jira/browse/HIVE-17167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107845#comment-16107845
]
Vihang Karajgaonkar commented on HIVE-17167:
--------------------------------------------
Yes, without sub-classing I agree we cannot enforce this in code. Given that
users can still do a conf.get("key") instead of MetastoreConf.getX(conf, key),
adding a check for inconsistent values in MetastoreConf.getX() may not work for
all the cases and will only add to the confusion.
> Create metastore specific configuration tool
> --------------------------------------------
>
> Key: HIVE-17167
> URL: https://issues.apache.org/jira/browse/HIVE-17167
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
> Attachments: HIVE-17167.patch
>
>
> As part of making the metastore a separately releasable module we need
> configuration tools that are specific to that module. It cannot use or
> extend HiveConf as that is in hive common. But it must take a HiveConf
> object and be able to operate on it.
> The best way to achieve this is using Hadoop's Configuration object (which
> HiveConf extends) together with enums and static methods.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
