[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14623370#comment-14623370
]
Jack Krupansky commented on CASSANDRA-6477:
-------------------------------------------
bq. we allow <= 1 non-pk column in a MV partition key however the error message
we log on multiple attempts reads "Cannot include non-primary key column '%s'
in materialized view partition key". We should log that <= 1 are allowed
instead.
Wow, is that really true? It sounds like a crippling restriction. Is that
simply a short-term expediency for the initial elease or a hard-core long-term
restriction?
Just as an example if I had a table with name, address and id, with id as the
primary key, I couldn't have an MV with just name or just address or just name
and address as the partition key, right?
In particular, this restriction seems to preclude pure inverted index MVs -
where the non-key content of the row is used to index the key for the row.
Still waiting to read an updated CQL spec - especially any such limitations.
> Materialized Views (was: 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
> Assignee: Carl Yeksigian
> Labels: cql
> Fix For: 3.0 beta 1
>
> Attachments: test-view-data.sh, 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
(v6.3.4#6332)
