[jira] [Commented] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it.

["Pradeep Agrawal (JIRA)" <ji...@apache.org>]

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

Pradeep Agrawal commented on RANGER-1612:
-----------------------------------------

committed to Apache Ranger master branch : https://github.com/apache/ranger/commit/0f0bfc6dcece0c19d353cc54c5d08416afa38493
committed to Apache Ranger 0.7 branch : https://github.com/apache/ranger/commit/cf01599b8724e080bcb760ef207fcf9fe9943396

> When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it.
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: RANGER-1612
>                 URL: https://issues.apache.org/jira/browse/RANGER-1612
>             Project: Ranger
>          Issue Type: Bug
>          Components: Ranger
>            Reporter: Anuja Leekha
>            Assignee: Pradeep Agrawal
>              Labels: ranger
>             Fix For: 1.0.0, 0.7.1
>
>         Attachments: RANGER-1612-1.patch
>
>
> During the migration of hive service def When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it. 
> Now, hive service def has changed (because URL as a resource is added to it). So when servicedef is updated, enableDenyPolicies property is updated in the database to be "false" which should not happen.
> The migration script for service-def needs to check what the real value of this property is in the database and preserve it across migration.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)