Thankyou so much,Sushanth.
I GOT IT ( :) )
At 2016-08-20 07:24:10, "Sushanth Sowmyan" wrote:
>One more addition to what Thejas mentioned -
>BitSetCheckAuthorizationProvider was the old legacy method of
>authorization in hive that was replaced in use-intent by
>SQLStandardAuthorization. I thin
One more addition to what Thejas mentioned -
BitSetCheckAuthorizationProvider was the old legacy method of
authorization in hive that was replaced in use-intent by
SQLStandardAuthorization. I think we should look to deprecating and
removing that now.
In general, if you want conventional db-like gr
1 - if it set to true, you need to manager permissions in two places for
users, using grant/revoke on tables, and file system permissions as well,
and keep them in sync. That will be a headache.
Moreover, the main intent for sql std auth is to be able to provide fine
grained access control using vi
Hi,all:
I have a few questions about hive authentication and authorization:
(1)why do we need to set hive.server2.enable.doAs=false in SQL-Standard Based
Authorization ?
(2)when set hive.server2.enable.doAs=false in SQL-Standard Based
Authorization,the beeline way to connecte HS2,
the queri
