ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pradeep Agrawal (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (RANGER-1612) When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies" is returned as "false" if there is no value set for it.
Date Fri, 26 May 2017 09:04:04 GMT

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

Pradeep Agrawal updated RANGER-1612:
------------------------------------
    Summary: When servicedef is accessed, one of the properties "enableDenyAndExceptionsInPolicies"
is returned as "false" if there is no value set for it.  (was: When servicedef is accessed,
one of the properties "enableDenyPolicies" is returned as "false" if there is no value set
for it.)

> 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
"enableDenyPolicies" 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)

Mime
View raw message