[
https://issues.apache.org/jira/browse/SENTRY-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15328636#comment-15328636
]
Sravya Tirukkovalur commented on SENTRY-1323:
---------------------------------------------
Ok, here is the cause:
https://issues.apache.org/jira/secure/attachment/12698781/HIVE-9350.5.patch#file-13
{noformat}
738 private void setAuthorizerV2Config() throws HiveException {
739 // avoid processing the same config multiple times, check marker
740 if (conf.get(CONFIG_AUTHZ_SETTINGS_APPLIED_MARKER,
"").equals(Boolean.TRUE.toString())) {
741 return;
742 }
743 conf.setVar(ConfVars.METASTORE_FILTER_HOOK,
744
"org.apache.hadoop.hive.ql.security.authorization.plugin.AuthorizationMetaStoreFilterHook");
745
746 authorizerV2.applyAuthorizationConfigPolicy(conf);
747 // update config in Hive thread local as well and init the
metastore client
748 try {
749 Hive.get(conf).getMSC();
750 } catch (Exception e) {
751 // catch-all due to some exec time dependencies on session state
752 // that would cause ClassNoFoundException otherwise
753 throw new HiveException(e.getMessage(), e);
754 }
755
756 // set a marker that this conf has been processed.
757 conf.set(CONFIG_AUTHZ_SETTINGS_APPLIED_MARKER,
Boolean.TRUE.toString());
758 }
759
{noformat}
And we are calling the above function if authorizer = null, which seems to be
null in Sentry deployments. [~dapengsun], [~sircodesalot] are you familiar with
this part of the Hive code?
> Bump the hive version to 1.2.0
> ------------------------------
>
> Key: SENTRY-1323
> URL: https://issues.apache.org/jira/browse/SENTRY-1323
> Project: Sentry
> Issue Type: Sub-task
> Reporter: Sravya Tirukkovalur
> Assignee: Sravya Tirukkovalur
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1323.0.patch
>
>
> Deserializer as part of Hive-7973 work has some bugs in 1.1.0. For example:
> deserializer.getAlterTableMessage fails with JsonMappingException
> After some debugging, I confirmed that it is due to the fact that
> JSONAlterTableMessage does not have a default constructor.
> Seems like this is fixed as part of HIVE-10227 (1.2.0). So would be best to
> move to hive 1.2.0.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
