aid to admit that I LOVE this feature. Exactly what a data
> engine should be able to do – stop bad behavior.
>
>
>
> Sean R. Durity
>
>
>
> *From:* Aaron Ploetz
> *Sent:* Thursday, June 23, 2022 3:22 PM
> *To:* user@cassandra.apache.org
> *Subject:* [EXTERNAL
I'm not afraid to admit that I LOVE this feature. Exactly what a data engine
should be able to do - stop bad behavior.
Sean R. Durity
From: Aaron Ploetz
Sent: Thursday, June 23, 2022 3:22 PM
To: user@cassandra.apache.org
Subject: [EXTERNAL] Re: Guardrails in Cassandra 4.1 Alpha
Ahh...yes, my
Ahh...yes, my default "aaron" user is indeed a SUPERUSER.
Ok, so I created a new, non-superuser and tried again...
> SELECT * FROm stackoverflow.movies WHERE title='Sneakers (1992)' ALLOW
FILTERING;
InvalidRequest: Error from server: code=2200 [Invalid query]
message="Guardrail allow_filtering
Hi Aaron,
Guardrails are not applied to superusers. The default user is a superuser,
so to see guardrails in action you need to create and use a user that is
not a superuser.
You can do that by setting, for example, these properties on cassandra.yaml:
authenticator: PasswordAuthenticator
