[
https://issues.apache.org/jira/browse/CASSANDRA-16898?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17406771#comment-17406771
]
Benjamin Lerer commented on CASSANDRA-16898:
--------------------------------------------
|| Branch || CI ||
| [PR|https://github.com/apache/cassandra/pull/1175] |
[j8|https://app.circleci.com/pipelines/github/blerer/cassandra/190/workflows/e5f4d1a7-4c7c-43ff-a20b-111ca209e3cb]
[j11|https://app.circleci.com/pipelines/github/blerer/cassandra/190/workflows/9c18ded2-e9fe-497c-acb2-bc565e45dc5e]
|
> The clustering order logic in Materialized view creation changed in 4.0
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-16898
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16898
> Project: Cassandra
> Issue Type: Bug
> Components: Feature/Materialized Views
> Reporter: Benjamin Lerer
> Assignee: Benjamin Lerer
> Priority: Normal
>
> Before 4.0, when a Materialized view was created with no {{CLUSTERING ORDER}}
> specified the clustering order was based on the base table clustering order
> (see [3.11
> code|https://github.com/apache/cassandra/blob/cassandra-3.11/src/java/org/apache/cassandra/cql3/statements/CreateViewStatement.java#L108]).
> In 4.0 this behaviour changed and the clustering order was defaulted to ASC
> for all columns.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
