cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-10441) Move stress tool into it's own repository and manage dependency on Cassandra externally
Date Fri, 23 Oct 2015 16:16:27 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-10441.
----------------------------------------
    Resolution: Won't Fix

I hear you, but since stress's primary purpose is to inform C* development, I don't think
moving it out of tree makes sense.  Among other reasons, we play pretty fast and loose with
compatibility and we'd like to keep it that way.

> Move stress tool into it's own repository and manage dependency on Cassandra externally
> ---------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-10441
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10441
>             Project: Cassandra
>          Issue Type: Wish
>          Components: Tools
>            Reporter: Nitsan Wakart
>            Priority: Minor
>
> This will:
> 1. Allow distinct release/maintenance/contribution cycles
> 2. Prevent accidental dependencies from Cassandra into the stress tool
> 3. Isolate performance changes in Cassandra from changes to stress tool
>  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message