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

Josh McKenzie commented on CASSANDRA-17967:
-------------------------------------------

{quote}cassandra itself gives a very convoluted error message which mostly 
suggests to use "ALLOW FILTERING" clause. So that is the main reason we are 
going towards this new guardrail - so having a custom message is not such a bad 
idea.
{quote}
I agree with the problem statement and disagree with the proposed solution. We 
should clean up our default error message + make it more clear in the guardrail 
message why we think ALLOW FILTERING is by default a bad idea, perhaps even 
linking to documentation that helps educate the user on why and how ALLOW 
FILTERING doesn't scale.

Asking each operator or user to shore up our insufficient base error messaging 
isn't enough in my opinion. We can do better. :)

> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to