[
https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17504000#comment-17504000
]
Caleb Rackliffe commented on CASSANDRA-17370:
---------------------------------------------
[~savni_nagarkar] [~adelapena] Looks like Apache CI is [running out of disk
again|https://ci-cassandra.apache.org/view/patches/job/Cassandra-devbranch/1484/].
I guess I'll just get my review done and do a CircleCI run w/ HIGHRES (and the
current CASSANDRA-17351 workaround) after that...
> Add flag enabling operators to restrict use of ALLOW FILTERING in queries
> -------------------------------------------------------------------------
>
> Key: CASSANDRA-17370
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17370
> Project: Cassandra
> Issue Type: Improvement
> Components: CQL/Semantics, Feature/Guardrails
> Reporter: Savni Nagarkar
> Assignee: Savni Nagarkar
> Priority: Normal
> Fix For: 4.x
>
>
> This ticket adds the ability for operators to disallow use of ALLOW FILTERING
> predicates in CQL SELECT statements. As queries that ALLOW FILTERING can
> place additional load on the database, the flag enables operators to provide
> tighter bounds on performance guarantees. The patch includes a new yaml
> property, as well as a hot property enabling the value to be modified via JMX
> at runtime.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
