[
https://issues.apache.org/jira/browse/CASSANDRA-2474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13172307#comment-13172307
]
Pavel Yaskevich commented on CASSANDRA-2474:
--------------------------------------------
bq. but for users who are coming from thrift they will be asking "how do i
access data from my current data model?"
We can support special command to set metadata about CF transposition,
something like "TRANSPOSE <cf> AS (col, ...) WITH SPARSE (<id>, ...)" or "ALTER
TABLE <cf> SET TRANSPOSED AS (col, ...) WITH SPARSE (<id>, ...)"
bq. On the negative side, this approach feels a bit too restrictive since you
MUST use the same kind of schema across all rows within a CF. What if a user
doesn't know what the sparse columns will be ahead of time?
User will be able to add sparse columns using "ALTER TABLE" command.
bq. Also, I know that's best practice but want to make the point, what if a
user wants to access data in composite form and "raw" mode, should we support
multiple "views" on the CF?
Can you elaborate "raw" 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
