[ https://issues.apache.org/jira/browse/CASSANDRA-12681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15518275#comment-15518275 ]
Jeff Jirsa commented on CASSANDRA-12681: ---------------------------------------- As far as I can tell, modern versions of titan are no longer abusing schema metadata: [by default they're using SimpleStrategy with no options|https://github.com/thinkaurelius/titan/blob/titan10/titan-cassandra/src/main/java/com/thinkaurelius/titan/diskstorage/cassandra/AbstractCassandraStoreManager.java#L83-L93], and probably relying on users to set anything beyond SimpleStrategy, and I see no custom strategy options being passed. > Reject empty options and invalid DC names in replication configuration while > creating or altering a keyspace. > ------------------------------------------------------------------------------------------------------------- > > Key: CASSANDRA-12681 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12681 > Project: Cassandra > Issue Type: Improvement > Components: Distributed Metadata > Reporter: Nachiket Patil > Assignee: Nachiket Patil > Priority: Minor > Attachments: trunkpatch.diff, v3.0patch.diff > > > Add some restrictions around create / alter keyspace with > NetworkTopologyStrategy: > 1. Do not accept empty replication configuration (no DC options after class). > Cassandra checks that SimpleStrategy must have replication_factor option but > does not check that at least one DC should be present in the options for > NetworkTopologyStrategy. > 2. Cassandra accepts any random string as DC name replication option for > NetworkTopologyStrategy while creating or altering keyspaces. Add a > restriction that the options specified is valid datacenter name. Using > incorrect value or simple mistake in typing the DC name can cause outage in > production environment. -- This message was sent by Atlassian JIRA (v6.3.4#6332)