cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-571) API for requesting sub-slices of a range of supercolumns
Date Mon, 11 Apr 2011 22:07:05 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-571?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-571.
--------------------------------------

    Resolution: Won't Fix

As we've figured out best practices around supercolumns, this isn't really necessary.  (Supercolumns
are best used for denormalizing data that is accessed at the same time.)

> API for requesting sub-slices of a range of supercolumns
> --------------------------------------------------------
>
>                 Key: CASSANDRA-571
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-571
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Priority: Minor
>
> Suhail Doshi wrote in a comment to CASSANDRA-570 (a different issue):
> Ability to slice a column and specify an exact super column key, for example:
> column_1 {
>    sc1: {}
> }
> column_2 {
>    sc1: {}
>    sc2: {}
> }
> Be able to slice by "column_1" to "column_2" but instead of grabbing every column, grab
only super column "sc1" from each? The reasoning is that it's terrible to have to slice by
column and get *every* super column and have it held in memory for the client application.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message