[
https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932508#comment-13932508
]
Benedict commented on CASSANDRA-6146:
-------------------------------------
bq. What was your setup?
I assume this was related to the fact that every single query failed (this was
because the bundled native driver is not the latest, so not compatible with
2.1) - possibly there's a problem with cleaning up of resources on error?
bq. We can create a templates for sure, but user will have to register them
manually
I only included templates because the "open" button seems to default to the
templates directory for some reason. Examples would be fine for now, it's
definitely not a show stopper that we don't have any templates, though they
would be nice to add.
bq. All those errors will be available in jmeter.log
Is there any way to separate the errored samples in the regular output from the
non-errored, just so it's clear? Not a single statement of mine succeeded, but
other than a little number in the top right corner I had no idea until I just
happened to click on it, and the mouse over said "show errors", but clicking
also displayed an empty error log, further suggesting it was probably fine and
just a normal count.
> CQL-native stress
> -----------------
>
> Key: CASSANDRA-6146
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6146
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Jonathan Ellis
> Fix For: 2.1 beta2
>
>
> The existing CQL "support" in stress is not worth discussing. We need to
> start over, and we might as well kill two birds with one stone and move to
> the native protocol while we're at it.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
