[
https://issues.apache.org/jira/browse/CASSANDRA-17650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556336#comment-17556336
]
Ekaterina Dimitrova edited comment on CASSANDRA-17650 at 6/20/22 11:30 AM:
---------------------------------------------------------------------------
Hi [~akin-tekeoglu]! Thanks for looking into this ticket. You are right about
that validation, but the question is whether batch_size_{_}fail{_}_threshold
needs it too or not. Please feel free to assign the ticket if you are
interested to work on it. Also, please, let me know if you need any help
was (Author: e.dimitrova):
Hi [~akin-tekeoglu]! Thanks for looking into this ticket. You are right about
that validation, but the question is whether batch_size_{_}fail{_}_threshold
needs it too or not. Please feel free to assign the ticket if you are
interested to work on it. Also, please, let me know if you need any hel
> Check startup and setter validations for batch_size_fail_threshold
> ------------------------------------------------------------------
>
> Key: CASSANDRA-17650
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17650
> Project: Cassandra
> Issue Type: Task
> Components: Local/Config
> Reporter: Ekaterina Dimitrova
> Priority: Low
> Fix For: 4.0.x, 4.1.x, 4.x
>
>
> During manual inspection it was noticed that batch_size_warn_threshold goes
> through checkValidForByteConversion, but this is not the case for
> batch_size_fail_threshold.
> This ticket is opened to check whether this is a bug or not.
> If it is confirmed it is a bug it needs to be fixed and the ticket can be
> changed to type bug. It seems that this validation was added as part of
> CASSANDRA-15470 to 4.0+. Maybe we also need it in 3.0 and 3.11?
> CC [~adelapena]
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
