cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Mon, 13 Jul 2015 15:52:08 GMT


Jonathan Ellis commented on CASSANDRA-6477:

A couple points from [~chbatey]'s [blog post|]:

bq. You can include any part of the original primary key in your MV primary key and a single
column that was not part of your original primary key

I think this is the same thing Jack is pointing out above.  Is there a compelling technical
reason behind this?  We lose a lot of flexibility if we can't have multiple non-pk columns
in either partition key or clustering.

bq. Any part of the original primary key you don't use will be added to the end of your clustering
columns to keep it a one to one mapping

IMO we should return an error and let them correct it rather than silently changing the definition
from what was given.

bq. If the part of your primary key is NULL then it won't appear in the materialised view

This also sounds like something we should fix or it will bite people in unpleasant ways.

> Materialized Views (was: 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 beta 1
>         Attachments:, users.yaml
> 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