Re: [DISCUSS] Add marker for Sentry server log

Hi HaoHao, Could you elaborate more about what is looking for here? Differentiate error, exception, failure, warning on server, client side, or system level. What we want to archive from using marker, the current logger has issues to indicate problem? Maybe by understanding these requirements can

[DISCUSS] Add marker for Sentry server log

Hi all, Is it a good idea to add different marker for different failures or unexpected behaviors for Sentry log? Any recommendation/guideline on what kinds of log marker we can have? Thanks a lot! Best, Hao

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

> On Oct. 7, 2016, 12:56 a.m., Sravya Tirukkovalur wrote: > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java, > > line 77 > > > > > > Shall we name this as

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

> On Oct. 11, 2016, 6:20 p.m., Li Li wrote: > > sentry-provider/sentry-provider-db/src/main/java/org/apache/sentry/service/thrift/HMSFollower.java, > > line 77 > > > > > > I think we should set fullUpdateComplete to

Sentry-jdk-1.7 - Build # 726 - Failure

The Apache Jenkins build system has built Sentry-jdk-1.7 (build #726) Status: Failure Check console output at https://builds.apache.org/job/Sentry-jdk-1.7/726/ to view the results.

Re: Review Request 52138: SENTRY-1463: Ensure HMS point-in-time snapshot consistency

--- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/52138/#review152171 ---

Re: Deleting old releases

I'm invoking lazy consensus here and removing 1.5.1. Colm. On Mon, Sep 12, 2016 at 10:09 AM, Colm O hEigeartaigh wrote: > I've removed 1.2.0, 1.3.0 + 1.4.0. Any opinions on removing 1.5.1 please? > > Colm. > > On Thu, Sep 8, 2016 at 9:31 AM, Colm O hEigeartaigh