cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4295) move checkaccess into statement.prepare
Date Tue, 26 Jun 2012 16:48:43 GMT


Sylvain Lebresne commented on CASSANDRA-4295:

So I will admit I'm a little uncomfortable committing something without having a solution
for the case where access right change over time (which the patch don't tackle unless I'm
misreading it). Access rights are a security feature, so it feel to me we don't want to start
to get too sloppy.

I'm almost inclined to say that the caching of access rights (which is basically what we're
talking about) is something the auth API should be in charge of doing (since it can do it

Or we make it part of the spec that access for prepared statement are checked during preparation
only, which is an option, but that sounds a bit weak to me. At least we shouldn't make that
decision lightly.
> move checkaccess into statement.prepare
> ---------------------------------------
>                 Key: CASSANDRA-4295
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: API
>    Affects Versions: 1.1.0
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 1.1.2
>         Attachments: CASSANDRA-4295.patch
> 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:!default.jspa
For more information on JIRA, see:


View raw message