cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tyler Hobbs <ty...@datastax.com>
Subject Re: Is compound index a planned feature in 3.0?
Date Wed, 31 Dec 2014 16:29:07 GMT
I don't think compound indexes are going to happen for 3.0.  Perhaps 3.1,
but they haven't really been discussed in depth.

On Fri, Dec 26, 2014 at 4:31 AM, ziju feng <pkdogcom@gmail.com> wrote:

> The global index JIRA actually mentions compound index but it seems that
> there is no JIRA created for this feature? Anyway, I think I should wait
> for 3.0 and see what does it bring to index. Thanks.
>
> On Fri, Dec 26, 2014 at 6:09 PM, DuyHai Doan <doanduyhai@gmail.com> wrote:
>
>> Many JIRA related to index are opened for 3.x
>>
>> Global indices: https://issues.apache.org/jira/browse/CASSANDRA-6477
>> Functional index: https://issues.apache.org/jira/browse/CASSANDRA-7458
>> Partial index: https://issues.apache.org/jira/browse/CASSANDRA-7391
>>
>> On Fri, Dec 26, 2014 at 10:49 AM, ziju feng <pkdogcom@gmail.com> wrote:
>>
>>> Compound index in MongoDB is really useful for qiery that involves
>>> filtering/sorting on multiple columns. I was wondering if Cassandra 3.0 is
>>> supposed to implement this feature.
>>>
>>> When I read through JIRA, I only found feature like CASSANDRA-6048
>>> <https://issues.apache.org/jira/browse/CASSANDRA-6048>, which allows
>>> using multiple single column indexes in a query by joining predicates.
>>> Compound index is more query driven and is closer to current
>>> application-maintained index table, which may provide better performance
>>> than single column index and can greatly simplify index maintenance during
>>> updates than index table.
>>>
>>> Any idea?
>>>
>>> Ziju
>>>
>>
>>
>


-- 
Tyler Hobbs
DataStax <http://datastax.com/>

Mime
View raw message