[
https://issues.apache.org/jira/browse/CASSANDRA-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985165#comment-13985165
]
Matt Stump commented on CASSANDRA-6559:
---------------------------------------
Allow filtering should be disabled by default and only allowed after the user
explicitly enables the behavior in cassandra.yaml. It's a major source of
escalations. 3 customers in the past 2 weeks. People either aren't heading,
reading the docs/warnings or think it doesn't apply to them.
> cqlsh should warn about ALLOW FILTERING
> ---------------------------------------
>
> Key: CASSANDRA-6559
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6559
> Project: Cassandra
> Issue Type: Bug
> Components: Tools
> Reporter: Tupshin Harper
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Fix For: 2.0.8
>
>
> ALLOW FILTERING can be a convenience for preliminary exploration of your
> data, and can be useful for batch jobs, but it is such an anti-pattern for
> regular production queries, that cqlsh should provie an explicit warn
> ingwhenever such a query is performed.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
