[
https://issues.apache.org/jira/browse/CASSANDRA-16898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Lerer updated CASSANDRA-16898:
---------------------------------------
Description: 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. (was: 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. )
> 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: [email protected]
For additional commands, e-mail: [email protected]