hive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vaibhav Gumashta (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-8173) HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
Date Fri, 17 Oct 2014 18:08:33 GMT

    [ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14175326#comment-14175326
] 

Vaibhav Gumashta commented on HIVE-8173:
----------------------------------------

[~thejas] Test failures are unrelated.

> HiveServer2 dynamic service discovery: figure out best ZooKeeper ACLs for security
> ----------------------------------------------------------------------------------
>
>                 Key: HIVE-8173
>                 URL: https://issues.apache.org/jira/browse/HIVE-8173
>             Project: Hive
>          Issue Type: Sub-task
>          Components: HiveServer2, JDBC
>    Affects Versions: 0.14.0
>            Reporter: Vaibhav Gumashta
>            Assignee: Vaibhav Gumashta
>            Priority: Critical
>              Labels: TODOC14
>             Fix For: 0.14.0
>
>         Attachments: HIVE-8173.1.patch, HIVE-8173.2.patch
>
>
> Currently while creating a znode for the ZooKeeper namespace and for server instances,
the create mode is: OPEN_ACL_UNSAFE - meaning anyone can read-write. Need to figure out how
a more restrictive model can be used: ideally the creator should be read/write/delete and
others should be read only 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message