Repeat

1 Version

Takes a count UInt64 on the first input and a value t on the second, and emits that value n times each paired tick via repeat. Output type is exactly t; a count of 0 emits nothing that tick.

How it fits

Typical backends

Replicate a constant a dynamic number of times sized by an upstream count, then gate the burst with a filter.

Fan one payload out into a burst and serialise each replicated event to JSON.

Caveats

Hard constraintThe first input is the UInt64 count and never reaches the output; the output type is exactly the second input t.
I/O contractA count of 0 produces no output for that tick, so downstream must tolerate zero-emission ticks.
LatencyOutput cadence is bursty: a large count produces a tight burst on the output stream, making downstream cadence irregular.
I/O contractBoth inputs are consumed once per paired tick and the value is replicated, not re-read between emissions.

Versions

0a2a922cdefaultlatestTransformation
10/12/2023