Table of Contents

Class DataStreamerOptions

Namespace
Apache.Ignite.Table
Assembly
Apache.Ignite.dll

Data streamer options.

public sealed record DataStreamerOptions : IEquatable<DataStreamerOptions>
Inheritance
DataStreamerOptions
Implements
Inherited Members

Constructors

DataStreamerOptions()

Initializes a new instance of the DataStreamerOptions class.

public DataStreamerOptions()

DataStreamerOptions(int, int, TimeSpan)

Data streamer options.

public DataStreamerOptions(int PageSize, int RetryLimit, TimeSpan AutoFlushInterval)

Parameters

PageSize int

The number of entries that will be sent to the cluster in one network call.

RetryLimit int

Retry limit for a batch. If a batch fails to be sent to the cluster, the streamer will retry it a number of times.

AutoFlushInterval TimeSpan

Auto flush interval - the period of time after which the streamer will flush the per-node buffer even if it is not full.

Fields

Default

Default streamer options.

public static readonly DataStreamerOptions Default

Field Value

DataStreamerOptions

Properties

AutoFlushInterval

Auto flush interval - the period of time after which the streamer will flush the per-node buffer even if it is not full.

public TimeSpan AutoFlushInterval { get; init; }

Property Value

TimeSpan

PageSize

The number of entries that will be sent to the cluster in one network call.

public int PageSize { get; init; }

Property Value

int

RetryLimit

Retry limit for a batch. If a batch fails to be sent to the cluster, the streamer will retry it a number of times.

public int RetryLimit { get; init; }

Property Value

int

SameKeyUpdateMode

Gets the mode controlling how same-key updates within one batch are handled.

By default (Squash), updates to the same key within a single batch are conflated and only the final state is applied — Continuous Query observes one event per affected key per batch.

With Preserve, repeated updates to the same key are separated into duplicate-free sub-batches, so Continuous Query observes one event per update. Updates for different keys can still be part of the same implicit transaction and share the same commit timestamp.

This option has no effect when streaming with a receiver: all items, including same-key duplicates, are passed to the receiver as-is, and any table updates are performed by the receiver code itself.

public DataStreamerSameKeyUpdateMode SameKeyUpdateMode { get; init; }

Property Value

DataStreamerSameKeyUpdateMode