[
https://issues.apache.org/jira/browse/CASSANDRA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285933#comment-13285933
]
Sylvain Lebresne commented on CASSANDRA-4295:
---------------------------------------------
bq. Most (all?) production implementations of the auth API are going to call
into a remote service to validate credentials, so that feels like something
worth optimizing away if we can.
Make sense. Though the "validated" business does suppose that we're able to say
when permission changes (I'm not sure all "production implementation of the
auth API" will provide that). Anyway, I'll give that a shot and we can readapt
a bit if that's not good enough for some auth implementation.
> move checkaccess into statement.prepare
> ---------------------------------------
>
> 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: Sylvain Lebresne
> Priority: Minor
> Fix For: 1.1.2
>
>
> there's no need to redo this every execution since the schema, tables, and
> users involved should all be immutable
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
