cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-3647) Support set and map value types in CQL
Date Mon, 16 Jul 2012 10:53:36 GMT


Pavel Yaskevich commented on CASSANDRA-3647:

bq. I think the current approach for collection representation at the Antlr level is reasonable.
It may be that Pavel's idea is better but I don't think we're going to make more progress
on that w/o actually coding it up. So if you want to give that a try in a separate ticket
Pavel, that's fine, but I don't think we should block this.

I believe we should block this and even more - I think we should make fine-grained sub-issues
to cover changes, like:

 - "Prepare marshal package for collection type support", which would add collection types
and make AbstractType happy with them;
 - "CQL3 grammar support for 'collection' operations on list/set/map", which would add a ANTLR
code to support required operations on the grammar level without using shaky combinations
like term/value/literal;
 - and this one would a glue for the two described above.

because as in the current state marshal is broken in a way that it requires instanceof checks,
this one pushes it to the whole new level by introducing functionality that "type" should
not have by it's nature e.g. "execute". I'm not fond of signing this up until we do something
about it or we are building a house without proper fundament.
> Support set and map value types in CQL
> --------------------------------------
>                 Key: CASSANDRA-3647
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Sylvain Lebresne
>              Labels: cql
>             Fix For: 1.2
> Composite columns introduce the ability to have arbitrarily nested data in a Cassandra
row.  We should expose this through CQL.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message