sentry-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasad Mujumdar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SENTRY-321) SentryMetastorePostEventListener should use sentry config to create SentryClient
Date Tue, 01 Jul 2014 01:42:24 GMT

    [ https://issues.apache.org/jira/browse/SENTRY-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14048409#comment-14048409
] 

Prasad Mujumdar commented on SENTRY-321:
----------------------------------------

Looks fine to me. This means for any Sentry config change to get effective, it will require
metastore service restart. Given that the sentry client config are pretty basic (eg server
address, provider etc), it should be okay to have that limitation.

+1


> SentryMetastorePostEventListener should use sentry config to create SentryClient
> --------------------------------------------------------------------------------
>
>                 Key: SENTRY-321
>                 URL: https://issues.apache.org/jira/browse/SENTRY-321
>             Project: Sentry
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Sravya Tirukkovalur
>            Assignee: Sravya Tirukkovalur
>             Fix For: 1.4.0
>
>         Attachments: SENTRY-321.patch
>
>
> When dropping a database, the following error is reported:
> {noformat}
> Error: Error while processing statement: FAILED: Execution Error, return code 1 from
org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Failed to connect to Sentry
service Config key sentry.service.client.server.rpc-address is required) (state=08S01,code=1)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message