Hi folks,
We are looking into some alternate design choices for HDFS Sentry sync to
be able to maintain the edit logs of both path updates(coming from HMS) and
perm updates (coming from Sentry) in a persistent state. The main
motivation is to make the HA cases more stable, as making the services
> On May 3, 2016, 12:21 a.m., Gregory Chanan wrote:
> > Note: these comments are based on the assumption you are implementing this
> > at the client layer. See my previous comments for why I think it's a
> > better idea right now to do this at the ProviderBackend layer.
As the code has
Have you tried enabling kerberos debugging on the server side?
On May 5, 2016 10:50 AM, "Sravya Tirukkovalur" wrote:
> Forwarding it to dev@s.a.o instead of dev@s.i.a.o
>
> -- Forwarded message --
> From: Sravya Tirukkovalur
> Date: Fri,
Thats a great suggestion Hao! I think we can achieve that by using labels.
But I am wondering what would the suggested workflow look like?
Label new feature jiras with "Design_review" and remove it when we have an
agreement on the design? One problem is design can be changed until the
patch is
Forwarding it to dev@s.a.o instead of dev@s.i.a.o
-- Forwarded message --
From: Sravya Tirukkovalur
Date: Fri, Apr 29, 2016 at 2:51 PM
Subject: Sentry web server - Spnego
To: dev
Hi Dapeng,
I am trying to use Sentry
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/47012/
---
(Updated May 5, 2016, 1:59 p.m.)
Review request for sentry.
Repository:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/45550/
---
(Updated May 5, 2016, 1:30 p.m.)
Review request for sentry.
Repository:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/47012/
---
Review request for sentry.
Repository: sentry
Description
---
Sentry