That means a separate metastore per User / different port. Please have in mind, anyone should maintain this. On top, the user has to choose the right JDBC connection. I have my doubt on such a installation ;)
On Nov 22, 2012, at 10:48 AM, Austin Chungath <[EMAIL PROTECTED]> wrote:
> Thanks Alex,
> But unfortunately I don't have kerberos implementation right now to try it
> I was wondering if we can create multiple metastore dbs in mysql and then
> for each user group make separate hive-site.xml which has the username and
> jdbc connection details. Do I make any sense? is something in these lines
> On Thu, Nov 22, 2012 at 2:11 PM, Alexander Alten-Lorenz <[EMAIL PROTECTED]
>> You could use SASL / kerberos implementation within HiveServer2. Depends
>> on a kerberosized cluster, too. Hive's metastore server provides the same
>> mechanism, but isn't fully multi connect ready.
>> Here's a link:
>> - Alex
>> On Nov 22, 2012, at 7:46 AM, Austin Chungath <[EMAIL PROTECTED]> wrote:
>>> I had been trying to set up a multi user environment for hive.
>>> I have set up the hive metastore db in MySQL and hive works.
>>> Consider this scenario:
>>> user1 has created a database data1
>>> user2 has created a database data2
>>> Now user2 logs into hive and he is able to see and delete database data2
>>> How do I prevent this?
>> Alexander Alten-Lorenz
>> German Hadoop LinkedIn Group: http://goo.gl/N8pCF
German Hadoop LinkedIn Group: http://goo.gl/N8pCF