Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Sun, 23 Jul 2017 15:18:00 +0000 (UTC)
From: "ZhaoYang (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12850050.1438199975000.310999.1500823080378@Atlassian.JIRA>
In-Reply-To: <JIRA.12850050.1438199975000@Atlassian.JIRA>
References: <JIRA.12850050.1438199975000@Atlassian.JIRA> <JIRA.12850050.1438199975883@jira-lw-us.apache.org>
Subject: [jira] [Updated] (CASSANDRA-9928) Add Support for multiple
 non-primary key columns in Materialized View primary keys
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Sun, 23 Jul 2017 15:18:06 -0000


     [ https://issues.apache.org/jira/browse/CASSANDRA-9928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ZhaoYang updated CASSANDRA-9928:
--------------------------------
    Component/s: Materialized Views

> 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
>          Components: Materialized Views
>            Reporter: T Jake Luciani
>              Labels: materializedviews
>             Fix For: 4.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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org