ranger-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhay Kulkarni (Jira)" <j...@apache.org>
Subject [jira] [Created] (RANGER-2814) RangerServiceResource signature should not include service-specific information
Date Thu, 30 Apr 2020 21:28:00 GMT
Abhay Kulkarni created RANGER-2814:

             Summary: RangerServiceResource signature should not include service-specific
                 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
             Fix For: master

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

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

View raw message