Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 25 Aug 2017 11:35:00 +0000 (UTC)
From: "ZhaoYang (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13097486.1503630167000.120214.1503660900212@Atlassian.JIRA>
In-Reply-To: <JIRA.13097486.1503630167000@Atlassian.JIRA>
References: <JIRA.13097486.1503630167000@Atlassian.JIRA> <JIRA.13097486.1503630167451@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (CASSANDRA-13798) Disallow filtering on
 non-primary-key base column for MV
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 25 Aug 2017 11:35:13 -0000


    [ https://issues.apache.org/jira/browse/CASSANDRA-13798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141491#comment-16141491 ] 

ZhaoYang edited comment on CASSANDRA-13798 at 8/25/17 11:34 AM:
----------------------------------------------------------------

| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] |
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & trunk.  The feature was added in 3.10 and the consequence may have been overlooked. It's better to revert it in 3.x/trunk, before more users start using it.

At the same time, I will work on a proper design (eg. multi-timestamp approach discussed in CASSANDRA-11500 and CASSANDRA-10226) for non-pk base column filtering and multiple non-pk base column in view pk.

[~pauloricardomg] [~brstgt] [~KurtG] what do you think?


was (Author: jasonstack):
| [trunk|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-trunk] |
| [3.11|https://github.com/jasonstack/cassandra/commits/CASSANDRA-13798-3.11] |
| [dtest|https://github.com/riptano/cassandra-dtest/commits/CASSANDRA-13798] |

The patch is to revert supporting non-pk base column filtering on MV on 3.11 & trunk.  The feature was added in 3.10 and the consequence may have been overlooked. It's better to revert it in 3.x/trunk, before more users start using it.

At the same time, I will work on a proper design (eg. multi-timestamp approach discussed in CASSANDRA-11500 and CASSANDRA-10226) for non-pk base column filtering and multiple non-pk base column in view pk.

> Disallow filtering on non-primary-key base column for MV
> --------------------------------------------------------
>
>                 Key: CASSANDRA-13798
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13798
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Materialized Views
>            Reporter: ZhaoYang
>            Assignee: ZhaoYang
>
> We should probably consider disallow filtering conditions on non-primary-key base column for Materialized View which is introduced in CASSANDRA-10368.
> The main problem is that the liveness of view row is now depending on multiple base columns (multiple filtered non-pk base column + base column used in view pk) and this semantic could not be properly support without drastic storage format changes. (SEE CASSANDRA-11500, [background|https://issues.apache.org/jira/browse/CASSANDRA-11500?focusedCommentId=16119823&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16119823])
> We should step back and re-consider the non-primary-key filtering feature together with supporting multiple non-PK cols in MV clustering key in CASSANDRA-10226.


--
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