cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "T Jake Luciani (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-6477) Materialized Views (was: Global Indexes)
Date Tue, 14 Jul 2015 04:12:09 GMT


T Jake Luciani commented on CASSANDRA-6477:

bq.  just leaving out data for a null value is broken.

I disagree. For example how do you take the token on a null partition key? (assuming your
partition key is a non-PK column)

bq. What if we decided that MV partition key will always be encoded as a tuple?

It doesn't solve the above problem and if you used it for clustering keys the query syntax
would be non-standard (you can't query by base name anymore)

bq. I don't see how NOT NULL works except as an extension of INSERTS ONLY

It wouldn't be any different than how we enforce it for PK today (if column is a PK column
it can't be null).  
The only restriction is you can't alter the table later to make a column not NOT NULL.  But
I'm not sure how tombstones would work, you could only update to a new value.

> 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