[
https://issues.apache.org/jira/browse/SENTRY-1938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16163193#comment-16163193
]
Hadoop QA commented on SENTRY-1938:
-----------------------------------
Here are the results of testing the latest attachment
https://issues.apache.org/jira/secure/attachment/12886648/SENTRY-1938.04.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/3282/console
This message is automatically generated.
> Sentry logs to provide more relevant information
> ------------------------------------------------
>
> Key: SENTRY-1938
> URL: https://issues.apache.org/jira/browse/SENTRY-1938
> Project: Sentry
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Vamsee Yarlagadda
> Assignee: Arjun Mishra
> Priority: Minor
> Labels: sentry-ha
> Attachments: SENTRY-1938.01.patch, SENTRY-1938.02.patch,
> SENTRY-1938.03.patch, SENTRY-1938.04.patch
>
>
> 1. HMSFollower
> * Print confirmation message (at INFO level) once full snapshot is persisted
> in the DB.
> * Print the message that HMSFollower is completely ready (after the initial
> pass of HMSFollower is done)
> 2. DBUpdateForwarder
> * Every log message should explicitly mention which type of events is it
> referring to (PERM or PATH) otherwise there is no way for us to differentiate
> between calls.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
