[
https://issues.apache.org/jira/browse/HIVE-17241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113131#comment-16113131
]
Alan Gates commented on HIVE-17241:
-----------------------------------
I propose a hybrid solution.
First, even in Hive 2 we no longer support Hadoop 1, so we are fine to drop it
completely from the standalone metastore.
In looking through the metastore shims three features are used:
# HDFS operations
# Secure password access from config files
# HadoopThriftAuthBridge and related code
None of these areas change from Hadoop 2 to 3, so we do not need to shim for
them. HDFS operations can be done directly in utility classes.
MetastoreConf.getPassword() already handles the secure password access.
HadoopThriftAuthBridge is harder. The only Hive module being referenced by the
stand alone metastore is the storage-api. It does not feel like
HadoopThriftAuthBridge fits in there. Talking to Vaibhav (who has spent the
most time with this code), the code has not changed significantly over the last
couple of years. Thus copying it is an option. This is about 1KLoC in size.
The other alternative is to move it into the standalone metastore (rather than
just copy it) and let HiveServer2 use it from there.
[~thejas], [~vgumashta], feedback?
> Change metastore classes to not use the shims
> ---------------------------------------------
>
> Key: HIVE-17241
> URL: https://issues.apache.org/jira/browse/HIVE-17241
> Project: Hive
> Issue Type: Sub-task
> Components: Metastore
> Reporter: Alan Gates
> Assignee: Alan Gates
>
> As part of moving the metastore into a standalone package, it will no longer
> have access to the shims. This means we need to either copy them or access
> the underlying Hadoop operations directly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
