kandra-test/io.kandra.test/KandraMultiDcTestcontainers/freshNetworkTopologyKeyspace

freshNetworkTopologyKeyspace

fun freshNetworkTopologyKeyspace(vararg classes: KClass<*>, localDatacenter: String = DC1, dcReplicationMap: Map<String, Int> = mapOf(DC1 to 1, DC2 to 1), statementBuilderConsistencyConfig: ConsistencyConfig = ConsistencyConfig()): KandraRuntimeHandle

Creates a fresh keyspace with genuine NetworkTopologyStrategy replication across both DCs (default {'dc1': 1, 'dc2': 1} -- one real replica per DC, the most RF a one-node-per-DC topology can actually serve reads/writes at; pass a higher factor only for metadata-only assertions, mirroring KandraTestcontainers.freshKeyspace's identical caveat), registers classes, and creates their tables against the DC named by localDatacenter.

Parameters

localDatacenter

which DC's contact point to bootstrap and connect through (DC1 or DC2). Matters for tests that then pause the other DC and expect local-DC operations to keep working, or pause this DC and expect failover/unavailability behavior.

dcReplicationMap

the NetworkTopologyStrategy replication map. Both DC names must be valid CQL identifiers; this is deliberately not re-validated here the way kandra-ktor's keyspaceDdl does for app-facing config -- this is test-only scaffolding.