[
https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004471#comment-14004471
]
Sylvain Lebresne commented on CASSANDRA-6146:
---------------------------------------------
bq. Create your tables with cqlsh -f, then run stress which can introspect
what you just created.
I actually like the idea of having the schema in the profile file because that
way we can ship with a bunch of reasonable and self contained stress
scenario/profile. If the schema is not in the profile file, then we'd have to
create some additional script file for each scenario that basically does the
'cqlsh -f' of whatever table we use for the profile. Possible, but having it
all self contained in one file is just more convenient.
That said, I can agree with stress not reinventing schema management, but I
don't think it has to. I'd also make the definitions optional as Jake
suggested. I'd typically change slightly the profile to always include the
keyspace and table name, so:
{noformat}
keyspace: stresscql
keyspace_definition: CREATE KEYSPACE stresscql WITH replication = {'class':
'SimpleStrategy', 'replication_factor': 1};
table: typestest
table_definition: CREATE TABLE typestest ...
{noformat}
That way the *_definition parts can be optional and the stress tool don't have
to parse the create statements to figure out the keyspace and table name.
Unrelated bikeshedding: I'd rename '-schema' to '-profile'.
> 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
> Assignee: T Jake Luciani
> Fix For: 2.1 rc1
>
> Attachments: 6146.txt
>
>
> 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)
