[RANGER-359] Policy validation: resource uniqueness: store resource signature of a policy in database for faster check

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.5.0
• Assignee: Alok Lal
• Reporter: Alok Lal
• Created: 01/Apr/15 17:58
• Updated: 06/May/15 16:14
• Resolved: 06/May/15 16:14

Description

Currently we iterate over all policies for a service, a generate its resource signature and use that to enforce uniquness. This can be computationally and space intensive if, say, there are several policies for a service or create/update of policies happens frequently. The resource signature of a policy could be kept in the database and kept up to date as resources change. Then a database level search could allow for doing this check cheaply and robustly.

Another way to reduce the space complexity could be to allow policy search command to return an Iterator instead of the collection of policies itself. This has some other challenges but is listed here for completeness.

Issue Links

• blocks: RANGER-356 Policy validation: resource uniqueness: to guard against someone editing the resource value directly, we should auto-heal the hash signatures of resources that are used for uniqueness check