I agree it is a useful layer and during my investigations in to
individual user connections from a spark application I was running some
tests with HiveServer2 and using Beeline I was able to authenticate the
users passed in correctly but when it came down to authorizing the
queries on the
The current scenario resembles a three tier architecture but without the
security of second tier. In a typical three-tier you have users connecting
to the application server (read Hive server2) are independently
authenticated and if OK, the second tier creates new ,NET type or JDBC
threads to
Yes, when creating a Hive Context a Hive Metastore client should be
created with a user that the Spark application will talk to the *remote*
Hive Metastore with. We would like to add a custom authorization plugin
to our remote Hive Metastore to authorize the query requests that the
spark
Hi,
What do you mean by Hive Metastore Client? Are you referring to Hive server
login much like beeline?
Spark uses hive-site.xml to get the details of Hive metastore and the login
to the metastore which could be any database. Mine is Oracle and as far as
I know even in Hive 2, hive-site.xml
As of Spark 1.6.0 it is now possible to create new Hive Context sessions
sharing various components but right now the Hive Metastore Client is
shared amongst each new Hive Context Session.
Are there any plans to create individual Metastore Clients for each Hive
Context?
Related to the question
