[
https://issues.apache.org/jira/browse/CASSANDRA-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15984667#comment-15984667
]
craig mcmillan commented on CASSANDRA-9928:
-------------------------------------------
currently i achieve this function by manually concatenating the extra keys i
want in the MV into a single text key - it's roughly workable, but timeuuids
can no longer be used to provide ordering, since they don't sort lexically
[~thobbs] solution would formalize and improve upon what i, and presumably many
others, are already having to do ?
> Add Support for multiple non-primary key columns in Materialized View primary
> keys
> ----------------------------------------------------------------------------------
>
> Key: CASSANDRA-9928
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9928
> Project: Cassandra
> Issue Type: Improvement
> Reporter: T Jake Luciani
> Labels: materializedviews
> Fix For: 3.11.x
>
>
> Currently we don't allow > 1 non primary key from the base table in a MV
> primary key. We should remove this restriction assuming we continue
> filtering out nulls. With allowing nulls in the MV columns there are a lot
> of multiplicative implications we need to think through.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
