[
https://issues.apache.org/jira/browse/CASSANDRA-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261328#comment-14261328
]
Philip Thompson commented on CASSANDRA-6559:
--------------------------------------------
I don't know if we should rely on CASSANDRA-8303 to close this, but if that is
implemented, this does feel redundant. I'm +0 on adding a cqlshrc option to not
question the user. The warning text should probably be printed immediately,
before the result set. If the query really is that large, they'll notice from
how long it takes to filter that its problematic. The problem with ALLOW
FILTERING is that it looks fine with small result sets, before moving to
production.
> 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
> Priority: Minor
> Labels: cqlsh
> Fix For: 2.0.12
>
>
> 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.3.4#6332)
