[
https://issues.apache.org/jira/browse/CASSANDRA-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14260432#comment-14260432
]
Aaron Ploetz commented on CASSANDRA-6559:
-----------------------------------------
"Maybe only require that on the first ALLOW FILTERING per cqlsh session"
It's a tough argument either way. We don't want to make Cassandra difficult or
inconvenient to use, yet the use of ALLOW FILTERING isn't exactly something we
want to encourage. The correct path is for users to build their queries and
column families the right way, and therefore not need ALLOW FILTERING at all.
Will pestering them with "are you sure" type questions on each query encourage
proper modeling by itself? Probably not.
So while I don't think that making ALLOW FILTERING easy to use is in our best
interests, I will agree that going with a warning on the first query is
probably the best option. And with the way I have the patch written, requiring
a 'Y' only once per session isn't hard to do.
I also like the further definition of the warning message. I'll add that in.
> 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)
