[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172426#comment-13172426
]
Jonathan Ellis commented on CASSANDRA-2474:
-------------------------------------------
bq. 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.
Right. But "schemaless" is a non-feature; "painless schema" is what people
care about. (1000 columns? No problem! ALTER without rewriting your data? No
problem!)
bq. This is the case I'm thinking of then. Would this be handled in CQL or a
"document" api?
I think it should be CQL, although we can support additional APIs on top of
that. CASSANDRA-3647
> 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
