Enum DataStreamerSameKeyUpdateMode
Controls how the data streamer handles multiple updates to the same key within one batch.
A batch is normally applied as a single implicit transaction with a single commit timestamp, so Continuous Query observes only the final state of each key in the batch. Preserve splits the batch so that every same-key update produces a separate commit and a separate Continuous Query event.
See SameKeyUpdateMode.
public enum DataStreamerSameKeyUpdateModeFields
Preserve = 1Same-key updates within one batch are detected and the batch is split so that each update lands in a separate transaction with its own commit timestamp. Continuous Query observes one event per update.
More expensive than Squash: each duplicate-key collision triggers an additional implicit transaction.
Squash = 0Default. Multiple updates to the same key within one batch are conflated to the final state. Continuous Query observes one event per affected key per batch.
This is the most performant mode, recommended when only the final state matters.