For now, Cassandra application developers have three options for compound (multi-column) indexing with Cassandra:
1. DataStax Enterprise Search, which uses Solr/Lucene under the hood. http://www.datastax.com/what-we-offer/products-services/datastax-enterprise/apache-solr 2. Stratio which uses Lucene directly: https://github.com/Stratio/stratio-cassandra 3. Stargate which also uses Lucene directly: http://tuplejump.github.io/stargate/ All three support Lucene queries in the WHERE clause of CQL SELECT. DSE also supports direct Solr HTTP API access for both queries and updates. -- Jack Krupansky On Wed, Dec 31, 2014 at 11:29 AM, Tyler Hobbs <ty...@datastax.com> wrote: > 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 <pkdog...@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 <doanduy...@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 <pkdog...@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/> >
