You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Vaibhav Gumashta (JIRA)" <ji...@apache.org> on 2014/10/17 01:53:34 UTC
[jira] [Commented] (HIVE-8173) HiveServer2 dynamic service
discovery: figure out best ZooKeeper ACLs for security
[ https://issues.apache.org/jira/browse/HIVE-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14174490#comment-14174490 ]
Vaibhav Gumashta commented on HIVE-8173:
----------------------------------------
cc [~thejas] [~ekoifman] [~dillidorai]
> 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
>
>
> 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)