[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172317#comment-13172317
]
T Jake Luciani commented on CASSANDRA-2474:
-------------------------------------------
bq. User will be able to add sparse columns using "ALTER TABLE" command.
Requiring a ALTER when you may not know what columns you have is too
restrictive. Example, a ETL from a 3rd party manufacturer that provides a
custom set of attributes per product: some standard (Unit Price, Model, Color,
etc) some specific (DPI, Shipping Size, Contrast Ratio). We don't want to go
back to having to know exactly what your data will look like before you can
write/read it. That's one of the important tenants of nosql I'd like to keep :)
bq. Can you elaborate "raw" mode?
I mean non-transposed mode.
> 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
