[
https://issues.apache.org/jira/browse/CASSANDRA-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14261286#comment-14261286
]
Aaron Ploetz commented on CASSANDRA-6559:
-----------------------------------------
Not a bad idea. But then some users would always have that option enabled.
And with that option enabled:
-if the warning text was output before the result set, it would be completely
lost/ignored with larger sets.
-if the warning text was output after the result set, it would push-up desired
results...again, only really an issue with larger sets. Although in this case,
the user would actually see it.
> 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)
