[
https://issues.apache.org/jira/browse/CASSANDRA-9921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14745953#comment-14745953
]
Alexandre Dutra commented on CASSANDRA-9921:
--------------------------------------------
Java driver PR [here|https://github.com/datastax/java-driver/pull/453].
Please note that this PR is still a work in progress. In particular, we do not
guarantee yet that all schema change events for MVs are correctly processed.
We also have a small problem: when a MV is created with {{CLUSTERING ORDER BY
... DESC}}, it seems that the relevant column in the {{columns}} table does not
have the expected {{ReversedType}}. See [this
test|https://github.com/datastax/java-driver/blob/java825/driver-core/src/test/java/com/datastax/driver/core/MaterializedViewMetadataTest.java#L75]
for an example. This makes the driver unable to recreate the original CREATE
MATERIALIZED VIEW statement.
> 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)
