[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172416#comment-13172416
]
T Jake Luciani commented on CASSANDRA-2474:
-------------------------------------------
bq. But that's exactly when you do know what columns you have.
In my example, when a new column is added to the file and inserted by the
loader, it's hidden from view till someone explicitly adds it as a sparse
column. That makes us no longer schemaless.
bq. Nested-but-not-transposed data aka "documents" is another separate case.
This is the case I'm thinking of then. Would this be handled in CQL or a
"document" api?
> 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: 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
