cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Brown (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4924) Make CQL 3 data accessible via thrift.
Date Tue, 06 Nov 2012 22:30:12 GMT


Jason Brown commented on CASSANDRA-4924:

My two cents: The initial impact of trying out the new feature (cql3), and not being to compare
it with something I already know (cassandra-cli) is a little confusing. I think Sylvain is
onto something when, in the other ticket, he mentions this may be a documentation issue, but
where would a new cql3 user (experienced with the old-school way) go to figure out what happened
to their shiny new cql3 data? 

While it's a little bit more work of supporting thrift, it might be worth it to ensure a smoother
on-ramp for cql3. Perhaps Aaron's idea of a config help lower the barrier to exit from thrift
for users.

Personally, I'd just want the cli, and clients like astyanax/hector, to be able to describe_keyspace
to show me the cql3 table exists, and reads would be nice, too, so I could confirm the cql3
data. Anything else is a freebie when trying to on-ramp to cql3. 
> Make CQL 3 data accessible via thrift.
> --------------------------------------
>                 Key: CASSANDRA-4924
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.2.0
>            Reporter: amorton
> Following the changes from CASSANDRA-4377 data created using CQL 3 is not visible via
the thrift interface. 
> This goes against the spirit of many comments by the project that "the thrift API is
not going away". These statements and ones such as "Internally, both CQL3 and thrift use the
same storage engine, so all future improvements to this engine will impact both of them equally."
( and the CQL3 and thrift examples given here gave the impression CQL 3 was
a layer on top of the core storage engine. It now appears to be an incompatible format change.

> It makes it impossible to explain to existing using users how CQL 3 stores it's data.

> It also creates an all or nothing approach to trying CQL 3. 
> My request is to make all data written by CQL 3 readable via the thrift API. 
> An example of using the current 1.2 trunk is below:
> {noformat}
> cqlsh:cass_college> CREATE TABLE UserTweets 
>                 ... (
>                 ...     tweet_id    bigint,
>                 ...     user_name   text,
>                 ...     body        text,
>                 ...     timestamp   timestamp,
>                 ...     PRIMARY KEY (user_name, tweet_id)
>                 ... );
> cqlsh:cass_college> INSERT INTO 
>                 ...     UserTweets
>                 ...     (tweet_id, body, user_name, timestamp)
>                 ... VALUES
>                 ...     (1, 'The Tweet', 'fred', 1352150816917);
> cqlsh:cass_college> 
> cqlsh:cass_college> 
> cqlsh:cass_college> select * from UserTweets;
>  user_name | tweet_id | body      | timestamp
> -----------+----------+-----------+--------------------------
>       fred |        1 | The Tweet | 2012-11-06 10:26:56+1300
> {noformat}
> and in the CLI
> {noformat}
> [default@cass_college] show schema;
> create keyspace cass_college
>   with placement_strategy = 'SimpleStrategy'
>   and strategy_options = {replication_factor : 3}
>   and durable_writes = true;
> use cass_college;
> [default@cass_college] list UserTweets;
> UserTweets not found in current keyspace.
> [default@cass_college] 
> {noformat}

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:

View raw message