[
https://issues.apache.org/jira/browse/CASSANDRA-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14273646#comment-14273646
]
Aleksey Yeschenko commented on CASSANDRA-8303:
----------------------------------------------
It's an alternative syntax, but I don't see how it's any different other than
cosmetically. It still produces the same number of new permissions in the end -
you just split its definition in two parts.
What would the new IAuthorizer look like? How would you properly compose
restricted/unrestricted permissions from all/keyspace/table?
I know it's doable, but it doesn't make things any simpler conceptually, and in
fact makes the code and more importantly the APIs, more complex.
> 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)
