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] [Commented] (CASSANDRA-6146) CQL-native stress
Date Tue, 20 May 2014 15:16:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14003420#comment-14003420
] 

Jonathan Ellis commented on CASSANDRA-6146:
-------------------------------------------

bq.  It's done by supplying the path to a yaml file containing the cql3 schema and queries

Why wouldn't we just introspect the schema from the cluster?  Note also that in most cases
we don't actually need to know the schema up front, to run a query (or to process a resultset
either).

See my first comment: https://issues.apache.org/jira/browse/CASSANDRA-6146?focusedCommentId=13786212&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13786212

> 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)

Mime
View raw message