[
https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17522508#comment-17522508
]
Josh McKenzie commented on CASSANDRA-17370:
-------------------------------------------
Only question I have is: did we decide to exclude system keyspaces from
Guardrails universally, just for ALLOW FILTERING, something else entirely?
Otherwise looks like Andres and David have covered anything I'd bring up on the
review.
+1 w/the tweaking to unit testing (I'm neutral on keeping in some of the
removing vestigial checked exceptions here vs. doing them _all_ in another
ticket. I don't think having a few here really hurts anything)
> 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
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> 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]
