[
https://issues.apache.org/jira/browse/CASSANDRA-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260363#comment-14260363
]
Philip Thompson commented on CASSANDRA-6559:
--------------------------------------------
Others can chime in, but I'm -1 for requiring users to enter 'Y' for every
single ALLOW FILTERING query they use in a single cqlsh session. If someone
does know what they're doing, they'll be frustrated by needing to do so for the
5-10 queries they may be issuing. Maybe only require that on the first ALLOW
FILTERING per cqlsh session, or only printing warning messages with no
additional user input required?
Additionally, the warning message gives absolutely no indication as to why a
user may not want to use ALLOW FILTERING. Consider adding a brief message that
ALLOW FILTERING queries are generally not acceptable for production use, such
as "ALLOW FILTERING detected. Queries of this type are not recommended for
production use. Please see the documentation. Are you sure you want to
continue?"
> 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)
