[ 
https://issues.apache.org/jira/browse/CASSANDRA-16467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380203#comment-17380203
 ] 

Caleb Rackliffe commented on CASSANDRA-16467:
---------------------------------------------

+1 to both patches

The only minor nit I have is that in the 3.11 version, where we have Unit 4.12 
available, I would use {{@Parameters(name="\{0\}")}} to make the test names a 
bit more descriptive. (i.e. If they fail, the input would be obvious.)

> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org

Reply via email to