cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Partitioned indexes
Date Mon, 31 Mar 2014 17:27:17 GMT


Benedict commented on CASSANDRA-6477:

[~jjordan] is that in response to me? Because I don't see how this would work: if both deleted
24 and inserted 25 and 26, then we now have a record of both 25 and 26 mapping to user1, despite
only one of them being true, and no means of tidying it up. So people can indefinitely look
up on both values. This is only resolved if we look up the original record after every 2i
result, which maybe was always the plan. I'm not sure.

> Partitioned indexes
> -------------------
>                 Key: CASSANDRA-6477
>                 URL:
>             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

View raw message