[
https://issues.apache.org/jira/browse/CASSANDRA-17370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17528317#comment-17528317
]
Andres de la Peña commented on CASSANDRA-17370:
-----------------------------------------------
One last CI run after rebasing:
||Patch||CI||
|[trunk|https://github.com/adelapena/cassandra/commit/14edb9f1b78381242cf2638cfff189e399af7630]|[j8|https://app.circleci.com/pipelines/github/adelapena/cassandra/1509/workflows/1b23e520-34b0-4501-8480-1dfe926cff09]
[j11|https://app.circleci.com/pipelines/github/adelapena/cassandra/1509/workflows/4f51b970-4a7a-442f-974c-c2ad55aece4b]|
It looks clean to me, all the failing tests are well-known.
> 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: 3.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.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
