[
https://issues.apache.org/jira/browse/CASSANDRA-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273757#comment-14273757
]
Jonathan Shook commented on CASSANDRA-8303:
-------------------------------------------
If we are being totally honest, the use of grant-style permissions here is on a
spectrum that merely includes strict authorization to access resources. The
user-facing elements of it are appropriate for limiting access to certain types
of operations, which can be anywhere on the spectrum. For this ticket, this
includes performance-affecting operations. Debating the usefulness of a
particular performance-affecting operation that can be easily categorized and
controlled seems moot. It is either performance-affecting or not. Unprepared
statements are clearly performance affecting.
So, we are already extending the traditional meaning of "grant." So be it. I
don't think that we can sacrifice the usefulness of the idiom based on
traditional labels. In many cases, it causes us pain as devs when users
conflate the concepts of security with other things, but this is not one of
those cases. Said a different way, If it were to be implemented in some way
other than "grant", then it's easy to imagine how this would be an unnatural
fit. It would be just another new thing for users to get their head around. To
me, this is clearly a case where embracing and extending the traditional idiom
is a win-win. It is *all* about limiting destructive potential, and so security
pedantry here is more of a hindrance than an enabler. That said, I agree with
[~slebresne].
The fact that it isn't as easy as the other permissions is an implementation
hurdle, and should not be a factor in whether we consider it a good idea. I
understand that it might not be there in the first cut. We've talked about this
one in particular without our team, and all of us so far think that it would be
a useful restriction to keep.
> Provide "strict mode" for CQL Queries
> -------------------------------------
>
> Key: CASSANDRA-8303
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8303
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Anupam Arora
> Fix For: 3.0
>
>
> Please provide a "strict mode" option in cassandra that will kick out any CQL
> queries that are expensive, e.g. any query with ALLOWS FILTERING,
> multi-partition queries, secondary index queries, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
