[
https://issues.apache.org/jira/browse/CASSANDRA-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802941#comment-14802941
]
Alexandre Dutra commented on CASSANDRA-9921:
--------------------------------------------
Updated java driver version
[here|https://github.com/datastax/java-driver/pull/459] with more robust
handling of schema change events for MVs. I strongly recommend updating the
bundled driver.
We observed a possible regression: in [this
test|https://github.com/datastax/java-driver/blob/java911/driver-core/src/test/java/com/datastax/driver/core/SchemaChangesTest.java#L236-L247]
the driver does receive an update event for the MV, and does issue a query to
update the MV metadata, but it seems that the MV is not being altered at all on
the C* side.
> Combine MV schema definition with MV table definition
> -----------------------------------------------------
>
> Key: CASSANDRA-9921
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9921
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Carl Yeksigian
> Assignee: Carl Yeksigian
> Labels: client-impacting, materializedviews
> Fix For: 3.0.0 rc1
>
> Attachments: 9921-unit-test.txt
>
>
> Prevent MV from reusing {{system_schema.tables}} and instead move those
> properties into the {{system_schema.materializedviews}} table to keep them
> separate entities.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
