Ddl
How the framework manages the structures it owns: a store's tables, collections and indexes (the logs, snapshots, timers, reservations, leases, checkpoints and the failure ledger, with their format records), the query indexes the Manifest declares, the Kafka topics and the ClickHouse tables. One setting, wow.ddl, overridden by wow.stores.<store>.ddl, wow.kafka.ddl and wow.clickhouse.ddl; each mode means the same everywhere.
Companion properties
Returns an immutable kotlin.enums.EnumEntries list containing the constants of this enum type, in the order they're declared.
Properties
Functions
Makes sure of the structure describe names as this mode says, with the backend's native checks: under AUTO creates it unless exists says it is there, and validates it when it is; under VALIDATE refuses it, naming it, when it does not exist, and validates it when it does; under NONE does nothing. A backend whose create is idempotent and checks what it finds leaves exists out: it then always creates.
Makes sure of the structure missing names as this mode says, with no round trip to ask whether it exists: under AUTO creates it, which must be idempotent (CREATE … IF NOT EXISTS, an index creation, a format record claimed), then validates it; under VALIDATE validates it alone; under NONE does nothing. validate checks the format of what it finds and answers whether the structure exists; one that does not refuses the startup, naming it.