cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Bailis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6477) Global indexes
Date Wed, 25 Jun 2014 00:01:30 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042865#comment-14042865
] 

Peter Bailis commented on CASSANDRA-6477:
-----------------------------------------

Just to follow up regarding our conversations at the NGCC: is there any interest at this point
in delivering any form of consistent index updates (e.g., beyond "eventually consistent" index
entries), or is the primary goal right now simply to get basic global index functionality
working?

Also, FWIW, though I have yet to think through [~benedict]'s second proposal, the "local CAS"
approach makes a lot of sense from my perspective insofar as you're willing to tolerate RF-1
redundant (but, importantly, idempotent!) index invalidations. I think this will work especially
well when, per [~tjake]'s proposal, you start partitioning the secondary index servers.

> Global indexes
> --------------
>
>                 Key: CASSANDRA-6477
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6477
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>             Fix For: 3.0
>
>
> Local indexes are suitable for low-cardinality data, where spreading the index across
the cluster is a Good Thing.  However, for high-cardinality data, local indexes require querying
most nodes in the cluster even if only a handful of rows is returned.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message