[
https://issues.apache.org/jira/browse/CASSANDRA-14931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16721602#comment-16721602
]
Jeff Jirsa commented on CASSANDRA-14931:
----------------------------------------
I'm not Benedict, but I have to imagine the significant value is the ability to
run (especially) correctness dtests on older versions that we'll need to
support upgrading to 4.0
I don't see why we'd do 2.2 - 3.0/3.11 need to be validated with respect to
4.0, but 2.2 does not.
The patch is a lot of lines, but seems like almost all of it is changing
try/catch to use the wrapper {{MBeanWrapper.instance.registerMBean()}}
Seems like the actual risk here is pretty small - maybe too much for 2.2, but
doesnt seem that bad for 3.0/3.11?
> Backport In-JVM dtests to 2.2, 3.0 and 3.11
> -------------------------------------------
>
> Key: CASSANDRA-14931
> URL: https://issues.apache.org/jira/browse/CASSANDRA-14931
> Project: Cassandra
> Issue Type: Improvement
> Components: Testing
> Reporter: Benedict
> Assignee: Benedict
> Priority: Major
> Fix For: 2.2.14, 3.0.18, 3.11.4
>
>
> The In-JVM dtests are of significant value, and much of the testing we are
> exploring with it can easily be utilised on all presently maintained
> versions. We should backport the functionality to at least 3.0.x and 3.11.x
> - and perhaps even consider 2.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
