cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-12952) AlterTableStatement propagates base table and affected MV changes inconsistently
Date Fri, 28 Jul 2017 10:35:00 GMT

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

ASF GitHub Bot commented on CASSANDRA-12952:
--------------------------------------------

GitHub user adelapena opened a pull request:

    https://github.com/apache/cassandra-dtest/pull/3

    Add tests for MVs when a column in the base table is renamed with ALTER TABLE (CASSANDRA-12952)

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/adelapena/cassandra-dtest 12952

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cassandra-dtest/pull/3.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3
    
----
commit 1dcd47bbe93446b58b503ede063641395f9bebfb
Author: Andrés de la Peña <a.penya.garcia@gmail.com>
Date:   2017-07-26T12:35:36Z

    Add tests for MV when a column in the base table is renamed with ALTER TABLE

----


> AlterTableStatement propagates base table and affected MV changes inconsistently
> --------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-12952
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-12952
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Distributed Metadata, Materialized Views
>            Reporter: Aleksey Yeschenko
>            Assignee: Andrés de la Peña
>             Fix For: 3.0.x, 3.11.x, 4.x
>
>
> In {{AlterTableStatement}}, when renaming columns or changing their types, we also keep
track of all affected MVs - ones that also need column renames or type changes. Then in the
end we announce the migration for the table change, and afterwards, separately, one for each
affected MV.
> This creates a window in which view definitions and base table definition are not in
sync with each other. If a node fails in between receiving those pushes, it's likely to have
startup issues.
> The fix is trivial: table change and affected MV change should be pushed as a single
schema mutation.



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


Mime
View raw message