[
https://issues.apache.org/jira/browse/SENTRY-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005061#comment-16005061
]
Hadoop QA commented on SENTRY-1757:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12867373/SENTRY-1757.002-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:green}Overall:{color} +1 all checks pass
{color:green}SUCCESS:{color} all tests passed
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2669/console
This message is automatically generated.
> 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
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1757.001-sentry-ha-redesign.patch,
> SENTRY-1757.002-sentry-ha-redesign.patch
>
>
> 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)
