[
https://issues.apache.org/jira/browse/SENTRY-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16126144#comment-16126144
]
Hadoop QA commented on SENTRY-1856:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12881783/SENTRY-1856.003.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/3155/console
This message is automatically generated.
> Persisting HMS snapshot and the notification-id to database in same
> transaction
> -------------------------------------------------------------------------------
>
> Key: SENTRY-1856
> URL: https://issues.apache.org/jira/browse/SENTRY-1856
> Project: Sentry
> Issue Type: Sub-task
> Components: Sentry
> Affects Versions: 2.0.0
> Reporter: kalyan kumar kalvagadda
> Assignee: Na Li
> Fix For: 2.0.0
>
> Attachments: SENTRY-1856.001.patch, SENTRY-1856.002.patch,
> SENTRY-1856.002.patch, SENTRY-1856.003.patch
>
>
> Currently notification-id associated with the snapshot and the actual HMS
> snapshot are persisted into database in a separate transactions.
> Ideally they should be updated in same transaction.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
