[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173624#comment-13173624
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. "just model it with dense composites" is not an option for the mview use
case, where adding new columns requires rebuilding the entire CF. That's a big
win for us, and I'm not willing to give it up.
Eric raised an interesting point on IRC -- is there a technical reason why the
"dense" CompositeType implementation can't just treat missing components as
null, allowing adding new columns in a straightforward "extension" of the
existing CT tuples?
(Dropping columns is trickier but doable: we'd need to keep the CT definition
the same, but add an "ignore these parts of the tuple" set to track columns
that are no longer relevant.)
If that's reasonable then I'm fine with dropping the whole "sparse" idea.
> CQL support for compound columns
> --------------------------------
>
> Key: CASSANDRA-2474
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2474
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Pavel Yaskevich
> Labels: cql
> Fix For: 1.1
>
> Attachments: 2474-transposed-1.PNG, 2474-transposed-raw.PNG,
> 2474-transposed-select-no-sparse.PNG, 2474-transposed-select.PNG,
> raw_composite.txt, screenshot-1.jpg, screenshot-2.jpg
>
>
> For the most part, this boils down to supporting the specification of
> compound column names (the CQL syntax is colon-delimted terms), and then
> teaching the decoders (drivers) to create structures from the results.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
