Thanks for the info. Those changes do not apply to Sentry because that is authorization metadata stored in HMS which Sentry does not consume at all. I initially was looking into those objects, though, but I found that those privileges must be set by the HMS clients in order to work. Also, I think the HivePrivilegeObject is used by the Hive authorization V2 privilege checks which Sentry does not use yet.
Btw, this would lead to a different conversation, but HMS already stores authorization metadata in it, why didn't Sentry use it before? Any history about Sentry you know about? On Mon, Mar 26, 2018 at 7:39 PM, Alexander Kolbasov <ak...@cloudera.com> wrote: > Just saw this: > > https://issues.apache.org/jira/browse/HIVE-19058 > > May be this has some relevance for FGP. >
