You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Andres de la Peña (Jira)" <ji...@apache.org> on 2022/03/11 17:49:00 UTC
[jira] [Created] (CASSANDRA-17430) Improve guardrails messages
Andres de la Peña created CASSANDRA-17430:
---------------------------------------------
Summary: Improve guardrails messages
Key: CASSANDRA-17430
URL: https://issues.apache.org/jira/browse/CASSANDRA-17430
Project: Cassandra
Issue Type: Improvement
Components: Feature/Guardrails
Reporter: Andres de la Peña
As it has been mentioned by [~JoshuaMcKenzie] , current guardrail messages don't mention that the warning or failure is due to the triggering of a specific guardrail. For example, some error messages are:
* {{Query for table %s with page size %s exceeds warning threshold of %s.}}
* {{Aborting query for table %s, page size %s exceeds fail threshold of %s.}}
* {{List operation requiring read before write is not allowed}}
This ticket aims to improve that behaviour so the messages contain a specific mention of guardrails, for example prepending a common prefix to the messages:
* {{Guardrail page_size violated: Query for table %s with page size %s exceeds warning threshold of %s.}}
* {{Guardrail page_size violated: Aborting query for table %s, page size %s exceeds fail threshold of %s.}}
* {{Guardrail read_before_write_list_operations violated: List operation requiring read before write is not allowed}}
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org