[
https://issues.apache.org/jira/browse/CASSANDRA-8303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14208759#comment-14208759
]
Anupam Arora commented on CASSANDRA-8303:
-----------------------------------------
Agreed. Kind of hard to define expensive as it will vary with each use case.
Our problem is that we have a shared infrastructure that runs multiple
applications. We have had our L3 & developer folks "accidentally" run queries,
while doing production triage, that had ALLOWS FILTERING, and multi-partition
queries with "IN". This has caused production issues because we see a large
spike in CPU on our servers and that starts to impacts every process hitting
that server. The challenge is that Cassandra allows such queries, so my request
is to create a "strict mode" that will make Cassandra reject such queries.
Hadoop Hive provides a similar mode that disallows certain types of queries.
> 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
>
> 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)
