[
https://issues.apache.org/jira/browse/CASSANDRA-5586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13664183#comment-13664183
]
Ryan McGuire edited comment on CASSANDRA-5586 at 5/22/13 3:25 PM:
------------------------------------------------------------------
Doing a few greps, it looks like the following tests use the cli:
* configuration_test
* super_column_cache_test
* cql_tests
I notice that some of the tests are specifically in regards to dealing with
data that was originally created with cassandra-cli (see
cql_tests:rename_test.) Part of me feels reluctant to remove tests that were
once valid scenarios.
was (Author: enigmacurry):
Doing a few greps, it looks like the following tests use the cli:
* configuration_test
* super_column_cache_test
* cql_tests
I notice that some of the tests are specifically in regards to dealing with
data that was originally created with cassandra-cli (see
cql_tests:rename_Test.) Part of me feels reluctant to remove tests that were
once valid scenarios.
> Remove cli usage from dtests
> ----------------------------
>
> Key: CASSANDRA-5586
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5586
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Brandon Williams
> Assignee: Ryan McGuire
> Priority: Minor
>
> The dtests in some situations fork the cli. With the cli essentially
> stagnant now, there's no need to do this when the same thing can be
> accomplished with a thrift or cql call. (ccm's convenience api for invoking
> the cli could probably also be removed at this point)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
