Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Mon, 15 Dec 2014 19:06:14 +0000 (UTC)
From: "Jeremy Hanna (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12754886.1415827802000.25957.1418670374084@Atlassian.JIRA>
In-Reply-To: <JIRA.12754886.1415827802000@Atlassian.JIRA>
References: <JIRA.12754886.1415827802000@Atlassian.JIRA>
 <JIRA.12754886.1415827802488@arcas>
Subject: [jira] [Commented] (CASSANDRA-8303) Provide "strict mode" for CQL
 Queries
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeremy Hanna commented on CASSANDRA-8303:
-----------------------------------------

I think the reasoning for Auth would be to give cluster administrators user based granularity and potentially a production user that can't use it by mistake.  Also the spark connector uses ALLOW FILTERING to get large blocks of data at a time.  It might be nice in that case to allow it for the user running the spark jobs, and disable it for other users.

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