You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Aleksei Zotov (Jira)" <ji...@apache.org> on 2021/07/11 20:00:09 UTC
[jira] [Commented] (CASSANDRA-16467) speculative retry should allow
more friendly params, allowing upgrade from 2.x not to break
[ https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17378774#comment-17378774 ]
Aleksei Zotov commented on CASSANDRA-16467:
-------------------------------------------
Just curious - why did you decide to not include "99p"?
The changes look good to me.
PS:
I'm not a committer, just checking existing patches as per Benjamin's email seeking for reviewers.
> 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: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org