[
https://issues.apache.org/jira/browse/CASSANDRA-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273548#comment-14273548
]
Aleksey Yeschenko commented on CASSANDRA-8303:
----------------------------------------------
bq. I agree that it's probably less useful than other restrictions, but I can
see it as useful for large organizations that want to enforce this easily. And
since it seems easy enough to include and without any real downside, I'd be
personally keen on including it from the start.
The downside is that it doesn't fit anywhere in the hierarchy, and it doesn't
fit the current model, code-wise - we call checkAccess() on an already
prepared statement. Would have to add another check to prepare() itself, which
is a mess - even if we did find a way to fit it somewhere in the hierarchy. So
-1 on using authz for limiting unprepared statements - in first version or
ever. This is just abuse of the authorization subsystem.
> 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)
