Package-level declarations
Types
How Wow reaches Kafka (kafka-clients only): the bootstrapServers, and properties passed to every producer and consumer as they are (security, client id, timeouts, batching, ...).
The PartitionedSource over Kafka consumers: made by create from KafkaOptions, consumers without a group that commit nothing, since the runtime assigns the partitions and keeps the offsets.
The TopicAdmin over a Kafka admin client, made by create from KafkaOptions:
The TopicProducer over a Kafka producer: made by create from KafkaOptions, an idempotent producer with acks=all.
The Kafka transport, type kafka: available once bootstrap-servers is set. Its settings, relative to its configuration (wow.kafka.*), are its options:
What a read of a Kafka partition does when the offset it is to read from is not in the partition: before its earliest retained offset (the topic's retention deleted what the checkpoint had yet to read), or past its end (the topic was deleted and created again, or truncated). Either way messages were lost, and the read never steps over them silently: whatever the policy, it logs an error, counts the gap (KafkaPartitionedSource.offsetGaps) and tells the node's observer of it (ObservedEvent.OffsetGap).
What a write to a topic survives: its partitions' fewest replicas (replicationFactor) and the replicas an acks=all write waits for (minInsyncReplicas, the broker's 1 when the topic sets none). A command accepted on a topic is durable once acknowledged only when both are at least 2: then losing one broker loses no acknowledged write.