[
https://issues.apache.org/jira/browse/CASSANDRA-6477?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14626038#comment-14626038
]
Sylvain Lebresne commented on CASSANDRA-6477:
---------------------------------------------
On the subject of {{null}} in primary keys, I'll first note that post-8099 we
do support {{null}} for clustering keys internally, so we can (and should) use
that.
Partition keys are arguably a bit more of a problem. My own preference would be
to actually do CASSANDRA-9796, as I think we should do that sooner or later
anyway and we could make {{null}} supported there in a somewhat reasonable way.
bq. I'm proposing that the encoding should be internal, not exposed to the user.
But MVs are currently directly exposed as read-only tables. So if we start
doing something that is internal only and not exposed to the user, this will
get hacky pretty quickly, forcing us to intercept the queries in
{{SelectStatement}} and do whatever translation is necessary. And I can
guarantee we'll regret that for the years to come. Which is why I would *much*
prefer a general solution à la CASSANDRA-9796.
> 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)
