[
https://issues.apache.org/jira/browse/CASSANDRA-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620570#comment-17620570
]
Josh McKenzie commented on CASSANDRA-17967:
-------------------------------------------
Opening Pandora's Box when you start talking about error codes. :) (see
CASSANDRA-3979 for instance).
Pretty sure [~blerer] spent some cycles on working on mapping error codes at
some point; there's so much in the system at this point that trying to "boil
the ocean" on the topic isn't viable.
My .02:
# A global "contact this email address if you'd like an exception to this
guardrail" that's operator configurable sounds clean and simple and provides a
lot of value
# I don't actually see the value in customizing the error messages on
guardrails; if the error messages we currently fire aren't descriptive of the
issue and don't properly educate the user we need to update and improve them
# We should talk about error codes on the dev ML so we can all publicly rant
about them together. ;)
> 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]
