You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pr@cassandra.apache.org by GitBox <gi...@apache.org> on 2022/11/07 10:56:45 UTC

[GitHub] [cassandra] adelapena commented on pull request #1972: CASSANDRA-17967 trunk: Add reason for guardrail triggering

adelapena commented on PR #1972:
URL: https://github.com/apache/cassandra/pull/1972#issuecomment-1305432126

   > @adelapena am I understanding this correctly that a user can't specify the `reason` to be used for a specific guardrail in the config? So you can hard code it but the user can't change it at his convenience?
   
   As it's mentioned on the ticket discussion, I don't think we should start using custom exception messages. There is no reason for that if the standard ones are clear enough, and custom messages can make it difficult to track where the exceptions come from.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: pr-unsubscribe@cassandra.apache.org
For additional commands, e-mail: pr-help@cassandra.apache.org