[jira] [Updated] (HIVE-13909) upgrade ACLs in LLAP registry when the cluster is upgraded to secure

2016-06-06 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-13909:

Fix Version/s: (was: 2.2.0)
   2.1.0

> upgrade ACLs in LLAP registry when the cluster is upgraded to secure
> 
>
> Key: HIVE-13909
> URL: https://issues.apache.org/jira/browse/HIVE-13909
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.1.0
>
> Attachments: HIVE-13909.01.patch, HIVE-13909.patch
>
>
> ZK model has authentication and authorization mixed together, so it's 
> impossible to set up acls that would carry over between unsecure and secure 
> clusters in the normal case (i.e. work for a specific users no matter the 
> authentication method).
> To support cluster updates from unsecure to secure, we'd need to change the 
> ACLs ourselves.



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


[jira] [Updated] (HIVE-13909) upgrade ACLs in LLAP registry when the cluster is upgraded to secure

2016-06-06 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-13909:

Target Version/s:   (was: 2.1.1)

> upgrade ACLs in LLAP registry when the cluster is upgraded to secure
> 
>
> Key: HIVE-13909
> URL: https://issues.apache.org/jira/browse/HIVE-13909
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.1.0
>
> Attachments: HIVE-13909.01.patch, HIVE-13909.patch
>
>
> ZK model has authentication and authorization mixed together, so it's 
> impossible to set up acls that would carry over between unsecure and secure 
> clusters in the normal case (i.e. work for a specific users no matter the 
> authentication method).
> To support cluster updates from unsecure to secure, we'd need to change the 
> ACLs ourselves.



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


[jira] [Updated] (HIVE-13909) upgrade ACLs in LLAP registry when the cluster is upgraded to secure

2016-06-06 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-13909:

  Resolution: Fixed
   Fix Version/s: 2.2.0
Target Version/s: 2.1.1
  Status: Resolved  (was: Patch Available)

Committed to master. Pending 2.1 commit...

> upgrade ACLs in LLAP registry when the cluster is upgraded to secure
> 
>
> Key: HIVE-13909
> URL: https://issues.apache.org/jira/browse/HIVE-13909
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Fix For: 2.2.0
>
> Attachments: HIVE-13909.01.patch, HIVE-13909.patch
>
>
> ZK model has authentication and authorization mixed together, so it's 
> impossible to set up acls that would carry over between unsecure and secure 
> clusters in the normal case (i.e. work for a specific users no matter the 
> authentication method).
> To support cluster updates from unsecure to secure, we'd need to change the 
> ACLs ourselves.



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


[jira] [Updated] (HIVE-13909) upgrade ACLs in LLAP registry when the cluster is upgraded to secure

2016-06-01 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-13909:

Status: Patch Available  (was: Open)

> upgrade ACLs in LLAP registry when the cluster is upgraded to secure
> 
>
> Key: HIVE-13909
> URL: https://issues.apache.org/jira/browse/HIVE-13909
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13909.01.patch, HIVE-13909.patch
>
>
> ZK model has authentication and authorization mixed together, so it's 
> impossible to set up acls that would carry over between unsecure and secure 
> clusters in the normal case (i.e. work for a specific users no matter the 
> authentication method).
> To support cluster updates from unsecure to secure, we'd need to change the 
> ACLs ourselves.



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


[jira] [Updated] (HIVE-13909) upgrade ACLs in LLAP registry when the cluster is upgraded to secure

2016-06-01 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-13909:

Attachment: HIVE-13909.01.patch

Rebased the patch based on some other commit.

> upgrade ACLs in LLAP registry when the cluster is upgraded to secure
> 
>
> Key: HIVE-13909
> URL: https://issues.apache.org/jira/browse/HIVE-13909
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13909.01.patch, HIVE-13909.patch
>
>
> ZK model has authentication and authorization mixed together, so it's 
> impossible to set up acls that would carry over between unsecure and secure 
> clusters in the normal case (i.e. work for a specific users no matter the 
> authentication method).
> To support cluster updates from unsecure to secure, we'd need to change the 
> ACLs ourselves.



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


[jira] [Updated] (HIVE-13909) upgrade ACLs in LLAP registry when the cluster is upgraded to secure

2016-06-01 Thread Sergey Shelukhin (JIRA)

 [ 
https://issues.apache.org/jira/browse/HIVE-13909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Shelukhin updated HIVE-13909:

Attachment: HIVE-13909.patch

[~prasanth_j] can you take a look?

> upgrade ACLs in LLAP registry when the cluster is upgraded to secure
> 
>
> Key: HIVE-13909
> URL: https://issues.apache.org/jira/browse/HIVE-13909
> Project: Hive
>  Issue Type: Bug
>Reporter: Sergey Shelukhin
>Assignee: Sergey Shelukhin
> Attachments: HIVE-13909.patch
>
>
> ZK model has authentication and authorization mixed together, so it's 
> impossible to set up acls that would carry over between unsecure and secure 
> clusters in the normal case (i.e. work for a specific users no matter the 
> authentication method).
> To support cluster updates from unsecure to secure, we'd need to change the 
> ACLs ourselves.



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