[
https://issues.apache.org/jira/browse/CASSANDRA-17967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620484#comment-17620484
]
Sarma Pydipally commented on CASSANDRA-17967:
---------------------------------------------
I agree that we should not have dedicated parameter for custom error message
for allow_filtering. But if we can come up with a generic framework, which can
be used for all other guardrails - i think will be helpful.
I just tagged this feature for 4.1 - but it can wait for a better design and
include it in 4.2 or 5.x - when it is ready.
Please keep this ticket open and we can discuss further or how to design this -
if it requires a deeper discussion with experts.
Also about error codes : I am not very familiar with internal process of how
cassandra handles internal exceptions, but it will be wonderful if there is a
framework which has standard error codes and associated short_error_message and
detailed_error_message info ... then we can decide if it dumps it on console or
it is written into logs. but having such error codes will allow the framework
to support for custom error messages. Any ideas ?
> 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]
