[
https://issues.apache.org/jira/browse/HIVE-17167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16107528#comment-16107528
]
Alan Gates commented on HIVE-17167:
-----------------------------------
The only way to enforce this in code is to subclass Configuration, which I
don't want to do as it makes it impossible to operate on existing HiveConf
objects. I could make it so that when one of the MetastoreConf.getX methods is
called, it checks to see if both the metastore key and the hive key are set and
to different values, and throws if so. But this doesn't prevent people using
just Configuration get and set methods and screwing things up.
> 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)
