[
https://issues.apache.org/jira/browse/RANGER-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pradeep Agrawal updated RANGER-2814:
------------------------------------
Fix Version/s: (was: master)
2.1.0
> RangerServiceResource signature should not include service-specific
> information
> -------------------------------------------------------------------------------
>
> Key: RANGER-2814
> URL: https://issues.apache.org/jira/browse/RANGER-2814
> Project: Ranger
> Issue Type: Bug
> Components: Ranger
> Affects Versions: master
> Reporter: Abhay Kulkarni
> Assignee: Abhay Kulkarni
> Priority: Major
> Fix For: 2.1.0
>
>
> RangerServiceResource objects represent a resource within scope of Ranger
> service in Ranger world. For efficient searching, resource contains a
> signature (which is a digest of its contents) which is computed at its
> creation as well as when it is updated.
> As the search for a resource is always carried out in the scope of Ranger
> service, there is no need to include service name (or service id) in its
> signature. In fact, having service name included in the signature makes
> upgrade/migration of tagged service resources very difficult.
> Along with removing service-name from the signature of.a service resource, a
> patch to migrate existing service resources to new signature is also needed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
