[ 
https://issues.apache.org/jira/browse/CASSANDRA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495090#comment-13495090
 ] 

Aleksey Yeschenko commented on CASSANDRA-4295:
----------------------------------------------

The patch implements the original suggestion (move checkaccess into 
statement.prepare) which we decided is not a good idea.
This is why I changed the status to Open on Saturday.
                
> 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
>            Priority: Minor
>             Fix For: 1.2.0 rc1
>
>         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

Reply via email to