[
https://issues.apache.org/jira/browse/CASSANDRA-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14258632#comment-14258632
]
Jeremy Hanna commented on CASSANDRA-8303:
-----------------------------------------
I hadn't noticed your latest comment [~mikea], but that's a good point and good
that we'd be able to enable/disable by role. Any user with an analytics role
for instance would have ALLOW FILTERING enabled.
Something that [~rssvihla] mentioned in terms of potential syntax for this in
cql:
{quote}
my idea for this syntax was based on grant/revoke execute and would entail
something like the following
GRANT MULTIPARTITION_QUERY ( "in" queries on partiton key not allowed but
inside a partition allowed, also could block broad select which is how counts
get expensive)
GRANT BATCH (could specifically reference logged and unlogged)
GRANT ALLOW_FILTERING
Pretty simple
Then one for the grouping of all crappy queries
GRANT UNSAFE_QUERIES
Obviously revoke would apply to all this type of groups.
Just spitballing not married to any of it, but grouping the common problem
queries into these groupings is a start.
On a per data center basis could just add a keyword at the end
GRANT MULTI_PARTITION on 'my_keyspace' in DC 'analytics'
{quote}
> 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)
