[
https://issues.apache.org/jira/browse/SENTRY-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15813751#comment-15813751
]
Hadoop QA commented on SENTRY-1538:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12846471/SENTRY-1538.002-sentry-ha-redesign.patch
against sentry-ha-redesign.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} mvn test exited 1
Console output:
https://builds.apache.org/job/PreCommit-SENTRY-Build/2236/console
This message is automatically generated.
> Create schema for storing HMS path change and Sentry permission change.
> -----------------------------------------------------------------------
>
> Key: SENTRY-1538
> URL: https://issues.apache.org/jira/browse/SENTRY-1538
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: sentry-ha-redesign
> Reporter: Alexander Kolbasov
> Assignee: Hao Hao
> Labels: hdfs-sync
> Fix For: sentry-ha-redesign
>
> Attachments: SENTRY-1538.001-sentry-ha-redesign.patch,
> SENTRY-1538.002-sentry-ha-redesign.patch
>
>
> As HMS Follower processes HMS notifications, they should be stored in Sentry
> DB. At a minimum we can only store notification ID, but for
> debugging/troubleshooting it is better to store actual JSON notification
> events as well.
> So this task about adding a schema for storing notifications. It its simplest
> form it will contain just notification ID as the primary key, possibly
> timestamp and the JSON notification event.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
