PartitionedSource
Reads the partitions of a topic from an offset: the port a Kafka-sourced subscription reads through. The runtime assigns the partitions to nodes by its own leases and keeps the offsets in its checkpoint store, so a source has no consumer group, commits nothing and keeps no position: each read starts where it is told.
partitions are the topic's partitions, in order.
partitionOf is the partition a message keyed
keylands in, as the TopicProducer of the same broker picks it: every message of a key is in that partition, so the records of one aggregate are found by re-scanning it.offsets are what a partition holds now: where a subscription that starts from the end starts, and whether an offset is still retained.
read emits the messages of one partition with an offset at or after
from, in offset order. A message that is no longer retained is skipped, so the first one emitted may be later thanfrom; offsets may also have gaps within a partition. The flow does not complete: after the messages written so far it waits for new ones, until it is cancelled. Bounded byuntil, it emits those beforeuntilonly and completes once it has passed them.