cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4295) Implement caching of authorization results
Date Sat, 10 Nov 2012 03:23:12 GMT

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

Aleksey Yeschenko updated CASSANDRA-4295:
-----------------------------------------

       Reviewer: jbellis  (was: slebresne)
    Description: 1.2 will come with default IAuthority implementation that stores permissions
in Cassandra, and each permission check will involve at least 1 Cassandra read. Some form
of authorization result caching is very important for this scenario.  (was: there's no need
to redo this every execution since the schema, tables, and users involved should all be immutable)
       Priority: Major  (was: Minor)
        Summary: Implement caching of authorization results  (was: move checkaccess into statement.prepare)
    
> Implement caching of authorization results
> ------------------------------------------
>
>                 Key: CASSANDRA-4295
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4295
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Aleksey Yeschenko
>             Fix For: 1.2.0
>
>         Attachments: CASSANDRA-4295.patch
>
>
> 1.2 will come with default IAuthority implementation that stores permissions in Cassandra,
and each permission check will involve at least 1 Cassandra read. Some form of authorization
result caching is very important for this scenario.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message