cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Shook (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8303) Provide "strict mode" for CQL Queries
Date Tue, 06 Jan 2015 18:52:35 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266550#comment-14266550
] 

Jonathan Shook commented on CASSANDRA-8303:
-------------------------------------------

It might be nice if the auth system was always in play (when that auth provider is set), but
the system defaults are applied to a virtual role with a name like "defaults". This cleans
up any layering questions by casting the yaml defaults into the authz conceptual model. If
a user isn't assigned to another defined role, they should be automatically assigned to the
defaults role.

Otherwise, explaining the result of layering them, even with precedence, might become overly
cumbersome. With it, you can use both.



> 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)

Mime
View raw message