[
https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14004492#comment-14004492
]
Benedict commented on CASSANDRA-6146:
-------------------------------------
bq. Okay, but why not define them by asking the cluster?
I'm not sure how you would do this? Just knowing the data types isn't enough to
do anything other than a very generic profile. That said, either making the CQL
to generate the tables optional, or generating it ourselves from the column
spec if it doesn't exist, seems appropriate. I think perhaps the Keyspace
should be left to the user to create, as the replication settings etc. are
cluster dependent, not profile dependent.
Note this is all pre-review; I've only briefly looked at the code, but I don't
want to miss the bike shedding.
> 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)
