You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@sentry.apache.org by "Na Li (JIRA)" <ji...@apache.org> on 2017/05/09 20:17:04 UTC
[jira] [Assigned] (SENTRY-1757) Avoid using local hive meta store
using wrong configuration
[ https://issues.apache.org/jira/browse/SENTRY-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Na Li reassigned SENTRY-1757:
-----------------------------
Assignee: Na Li
> Avoid using local hive meta store using wrong configuration
> -----------------------------------------------------------
>
> Key: SENTRY-1757
> URL: https://issues.apache.org/jira/browse/SENTRY-1757
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Na Li
> Assignee: Na Li
> Priority: Blocker
> Labels: security
>
> When HMSFollower.getMetaStoreClient() checks if it should create HiveMetaStoreClient, it uses the input configuration from SentryService.
> In real cluster deployment, the configuration does not contain value for "hive.metastore.uris", and therefore, HMSFollower never connects to the real meta store.
> In integration test, the configuration contains value for "hive.metastore.uris". Therefore integration tests pass.
> We need to check Hive configuration to avoid connecting to local meta store. And remove the value for "hive.metastore.uris" in integration test, so its behavior is the same as real cluster deployment.
> TestHDFSIntegrationBase.startSentry() `properties.put("hive.metastore.uris", "thrift://localhost:" + hmsPort);` is introduced in SENTRY-1429, SENTRY-1454, and SENTRY-1456
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)