[
https://issues.apache.org/jira/browse/SENTRY-2280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16525634#comment-16525634
]
Hadoop QA commented on SENTRY-2280:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12929460/SENTRY-2280.004.patch
against master.
{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/3936/console
This message is automatically generated.
> The request received in SentryPolicyStoreProcessor.sentry_notify_hms_event is
> null
> -----------------------------------------------------------------------------------
>
> Key: SENTRY-2280
> URL: https://issues.apache.org/jira/browse/SENTRY-2280
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.1.0
> Reporter: Na Li
> Assignee: Na Li
> Priority: Critical
> Attachments: SENTRY-2280.001.patch, SENTRY-2280.002.patch,
> SENTRY-2280.003.patch, SENTRY-2280.004.patch
>
>
> When running e2e test
> TestDbPrivilegeCleanupOnDrop.testRenameTablesWithinDBSinglePrivilege, I found
> the request received in SentryPolicyStoreProcessor.sentry_notify_hms_event is
> null
> There are multiple issues in fix from "SENTRY-2243: Extend the thrift
> definition for policy service to learn owner information"
> 1. The exception was thrown because the protocol_version was not set
> 2. TSentryAuthorizable.server was not set
> 3. TSentryHmsEventNotification.ownerType and ownerName are not set for table
> rename event
> As a result, the request received by server is null since thrift at server
> side cannot re-construct a valid request of type TSentryHmsEventNotification
> Once we fix the above issues, we need to make sure
> SentryPolicyStoreProcessor.sentry_notify_hms_event does not transfer owner in
> "alter table rename" event.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
