[
https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380680#comment-17380680
]
Ekaterina Dimitrova commented on CASSANDRA-16467:
-------------------------------------------------
The change moving from _toUpperCase_ to _toLowerCase_ was done as part of
b31845c4a7982358a7c5bfd9bcf572fda6c1bfa9 (CASSANDRA-9712). I didn't find any
reason for it, I suspect it was a mistake.
About [~azotcsit]'s question around the "99p". I think the reason is that we
fix here a bug/regression and that part was new in 4.0 ([~maedhroz] and
[~sumanth.pasupuleti], please, correct me if I am wrong). 3.0 and 3.11 are only
bug fixes.
[~sumanth.pasupuleti], do you mind to rebase and submit new CI run?
+1 on green CI, thank you!
> speculative retry should allow more friendly params, allowing upgrade from
> 2.x not to break
> -------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-16467
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16467
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Sumanth Pasupuleti
> Assignee: Sumanth Pasupuleti
> Priority: Normal
> Fix For: 3.0.x, 3.11.x
>
>
> 2.x speculative retry params are case insensitive, while 3.0 and 3.11 have
> added case sensitivity. As as result of this, one of our internal
> applications suffered an issue during
> C* upgrade from 2.x to 3.0.
> This ticket is to propose making 3.0 and 3.11 speculative_retry params case
> insensitive as well (essentially a slightly modified backport of
> CASSANDRA-13876, but not to allow something like "99p" which 4.0 allows)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
