[
https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Caleb Rackliffe updated CASSANDRA-16467:
----------------------------------------
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/e8f961f403a1a55a4837a576d744288599962d5a
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
Committed to...
...3.0 as
https://github.com/apache/cassandra/commit/e8f961f403a1a55a4837a576d744288599962d5a
...3.11 as
https://github.com/apache/cassandra/commit/de1d7d76a1c7682dfcec63a3e24e37e19d683bef
> 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.25, 3.11.11
>
>
> 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]
