cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremiah Jordan (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Global indexes
Date Mon, 20 Apr 2015 17:23:03 GMT


Jeremiah Jordan commented on CASSANDRA-6477:

My main issue is that "Global Index" means nothing to me, and I work in this space.  So I
think using the word materialized or denomarlized in the name would do a better job of making
clear what they are.  I don't really care what other words are used in the name ;).

That being said, I don't see a problem with VIEW.  While I agree that a "VIEW" in the SQL
world has more utility, so does "SELECT:.  Seems to me we give you a subset of VIEW, just
like we give you a subset of SELECT.  I don't think it is confusing to not be able to materialize
an arbitrary query that has joins and stuff in it, as we don't let you do that stuff in normal
queries.  And if we flesh this out over time with functions, composites, partial, etc, you
get closer and closer to what you can do with a traditional VIEW.

> Global indexes
> --------------
>                 Key: CASSANDRA-6477
>                 URL:
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: API, Core
>            Reporter: Jonathan Ellis
>            Assignee: Carl Yeksigian
>              Labels: cql
>             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