You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Sarma Pydipally (Jira)" <ji...@apache.org> on 2022/10/18 00:09:00 UTC

[jira] [Created] (CASSANDRA-17967) Guardrail: allow_filtering_custom_error_message

Sarma Pydipally created CASSANDRA-17967:
-------------------------------------------

             Summary: 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


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-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org