[
https://issues.apache.org/jira/browse/CASSANDRA-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13285778#comment-13285778
]
Jonathan Ellis commented on CASSANDRA-4295:
-------------------------------------------
I suppose, but they'd be *relatively* static, so adding a "validated" boolean
that we can negate when permissions change should be adequate.
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.
> 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
