cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tyler Hobbs (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-7248) Tuple type
Date Wed, 28 May 2014 21:11:02 GMT


Tyler Hobbs commented on CASSANDRA-7248:

bq. I've created a CQLTester class that is meant to be extended by CQL tests and that provide
convenience methods for execute and asserts. One of the nice property of it being that all
tests can be executed using either the prepared path or the normal, query string, path (without
writing every test twice that is).

Nice!  This looks great.


> Tuple type
> ----------
>                 Key: CASSANDRA-7248
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>            Reporter: Sylvain Lebresne
>            Assignee: Sylvain Lebresne
>              Labels: cql3
>             Fix For: 2.1 rc1
> For CASSANDRA-6875 we need to be able to talk about tuples values and types (for prepared
variables). Since we need it there, clients will need to support them anyway and so I think
it would be a lot cleaner to start supporting those more generally. Besides, having tuples
is a relatively simple and natural extension to what we have. I'll note in particular that
tuple have a close relationship to user type in the sense that a tuple will be really just
like an anonymous with no name for the fields and in particular a tuple value will be the
same than a user type value.
> The syntax would simply look like that:
> {noformat}
>     k int PRIMARY KEY,
>     v tuple<int, text, float>
> )
> INSERT INTO foo(k, v) VALUES(0, (3, 'bar', 2.1));
> {noformat}
> We can also add projections in selects if we want:
> {noformat}
> SELECT v[0], v[2] FROM foo WHERE k = 0;
> {noformat}
> but that can come later (after all, we still don't have projections for collections and
it's not a big deal).

This message was sent by Atlassian JIRA

View raw message