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

Alex Petrov commented on CASSANDRA-7826:
----------------------------------------

Would the updates and deletes for particular cells be within the scope of the 
ticket?

After talking to [~thobbs] there's also the question if we would like to 
support arbitrary updates or deletes right away, too. That would require new 
syntax for selecting the path for update or delete (maybe something like 
{{mymap['a']['b'][1]}}). Also, {{BufferCell/tombstone}} can most likely handle 
deletes as they are, without slices, as we'll always know at least the partial 
path, but if I understand it correctly, it will require additional logic for 
discarding columns whose partial path matches the path of the tombstone.

Also, most likely [7396|https://issues.apache.org/jira/browse/CASSANDRA-7396] 
will land before this patch, so it we might have to add support for selecting 
individual parts on arbitrary level (or just on the top level at first and 
leave the rest for the next iterations). So the question is what we'd like to 
have on the current step.

Right now, arbitrary nesting of maps is fully working (also, dtests and UDFs 
with nested structures are working). Non-frozen Set and List can be nested 
arbitrarily deep within the map, although nothing can be nested within Set or 
List. As was mentioned above. 

> support non-frozen, nested collections
> --------------------------------------
>
>                 Key: CASSANDRA-7826
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7826
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: CQL
>            Reporter: Tupshin Harper
>            Assignee: Alex Petrov
>              Labels: ponies
>             Fix For: 3.x
>
>
> The inability to nest collections is one of the bigger data modelling 
> limitations we have right now.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to