[
https://issues.apache.org/jira/browse/CASSANDRA-19592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sam Tunnicliffe updated CASSANDRA-19592:
----------------------------------------
Status: Changes Suggested (was: Review In Progress)
I think the approach is sound but we need to extend it to
{{CreateKeyspaceStatement}} {{CreateIndexStatement}}
The former may use {{default_keyspace_rf}} which can be set differently per
node, so we need to be explicit and encode whatever value the coordinator
resolves here.
Likewise, {{default_secondary_index}} injects the class of the index
implementation (or an alias for one) if none is specified (and
{{default_secondary_index_enabled: true}}, which is the default). This may also
have different values per-node, which causes different indexes to be created
locally.
I didn't find any other per-node settings that we need to mitigate in this way,
but I'll try to do another pass.
> Expand CREATE TABLE CQL on a coordinating node before submitting to CMS
> -----------------------------------------------------------------------
>
> Key: CASSANDRA-19592
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19592
> Project: Cassandra
> Issue Type: Bug
> Components: Cluster/Schema
> Reporter: Alex Petrov
> Assignee: Alex Petrov
> Priority: Normal
> Attachments: ci_summary.html
>
>
> This is done to unblock CASSANDRA-12937 and allow preserving defaults with
> which the table was created between node bounces and between nodes with
> different configurations. For now, we are preserving 5.0 behaviour.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
