[ 
https://issues.apache.org/jira/browse/CASSANDRA-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17619884#comment-17619884
 ] 

Ekaterina Dimitrova commented on CASSANDRA-17967:
-------------------------------------------------

[~oramad] reached out to me while I was away and I told him I think I saw 
already a guardrail for this but I did not have access to computer, etc at this 
point. 

I think he was looking for this functionality in 4.1(also stated in the 
description). 

So we have a few things going on here:
 * 4.1 is already in feature freeze, so we cannot add it there, unfortunately. 
But we can look into what we have in trunk - 5.0
 * trunk already has added allow_filtering_enabled as part of CASSANDRA-17370. 
That is the one [~jmckenzie], [~smiklosovic] and I had in mind
 * I guess we can keep this ticket for any further enhancements if we plan on 
any and update the description and get it out of triage of course

[~oramad], this is your ticket, let me know what you think :-) 

> Guardrail: allow_filtering_custom_error_message
> -----------------------------------------------
>
>                 Key: CASSANDRA-17967
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-17967
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Feature/Guardrails
>            Reporter: Sarma Pydipally
>            Priority: Normal
>
> in Apache Cassandra Release Version 4.1 :
> with "allow_filtering_enabled: false" option under guardrails :
> regular users cannot run queries with allow filtering clause in SELECT 
> commands. Users get following error message :
> <stdin>:1:InvalidRequest: Error from server: code=2200 [Invalid query] 
> message="Guardrail allow_filtering violated: Querying with ALLOW FILTERING is 
> not allowed"
> I propose for a new parameter in conf file : something like : 
> allow_filtering_custom_error_message and allow cluster operators to configure 
> custom message
> so if someone runs a SELECT command along with "ALLOW FILTERING"
> it should print ERROR : InvalidRequest:code=2202:message="STOP using 
> allow_filtering clause"
> so this will allow the operators to stop users from running allow filtering 
> as well as give them to configure a custom error message.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to