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

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

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

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

I think the question you're really pointing to is: Should we augment the Guardrails framework to allow operators to specify custom error messages?

[~adelapena] - have you given this any thought?

My initial reaction is that yeah, this is probably pretty useful. Being able to have an error message that says something like "Feature X is disabled because it causes problems Y. Email <gr...@domain.com> with your cluster name and use-case if you would like to apply for a specific exception" or something could be pretty useful.

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