You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Gautam Borad (JIRA)" <ji...@apache.org> on 2017/03/16 16:36:41 UTC
[jira] [Commented] (RANGER-1459) Ranger update policy API is
failing on Postgres / Oracle for case sensitive ACLs
[ https://issues.apache.org/jira/browse/RANGER-1459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928387#comment-15928387 ]
Gautam Borad commented on RANGER-1459:
--------------------------------------
Committed to ranger-0.7 : a44c04e436caadbe391cad957e9f4d70f66eb51e
Committed to master : f310aaf6bb7b81825ce2886ba4f16c13a09c603a
> Ranger update policy API is failing on Postgres / Oracle for case sensitive ACLs
> --------------------------------------------------------------------------------
>
> Key: RANGER-1459
> URL: https://issues.apache.org/jira/browse/RANGER-1459
> Project: Ranger
> Issue Type: Bug
> Components: admin
> Affects Versions: 0.7.0
> Reporter: Mehul Parikh
> Assignee: Gautam Borad
> Fix For: 0.7.1
>
> Attachments: RANGER-1459.patch
>
>
> When user tries to disable a ranger policy via REST API with postgres DB, then it gives this error, it works on MySQL though :
> {code}
> {u'msgDesc': u"Create: is not a valid access-type. policy='cl1_hive-87808627-ac26-499a-bea8-e99677a41889' service='cl1_hive'", u'statusCode': 1}
> {code}
> Mainly : This is a case sensitive issue on postgres / Oracle for ACLs, need to keep it consistent for GET and PUT calls for policies.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)