[
https://issues.apache.org/jira/browse/CASSANDRA-6559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14262318#comment-14262318
]
Aaron Ploetz edited comment on CASSANDRA-6559 at 12/31/14 6:49 PM:
-------------------------------------------------------------------
How about prompting the user on the first ALLOW FILTERING query, and then just
printing the warning afterward?
It just occurred to me, that implementing this without a .cqlshrc option
effectively eliminates command line based "-e" ALLOW FILTERING queries (unless
the user happens to be sitting right there and can answer 'Y'). So I'll also
add an option to disable the prompt (but not the warning).
{code}
[ui]
suppress_allow_filtering_prompt = true
{code}
was (Author: aploetz):
How about prompting the user on the first ALLOW FILTERING query, and then just
printing the warning afterward?
It just occurred to me, that implementing this without a .cqlshrc option
effectively eliminates command line based "-e" ALLOW FILTERING queries (unless
the user happens to be sitting right there and can answer 'Y'). So I'll also
add an option to disable the prompt (but not the warning).
{code}
[options]
suppress_allow_filtering_prompt = true
{code}
> 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)
