Class DataStreamerOptions

java.lang.Object
org.apache.ignite.table.DataStreamerOptions

public class DataStreamerOptions extends Object
Data streamer options. See DataStreamerTarget for more information.
  • Field Details

  • Method Details

    • builder

      public static DataStreamerOptions.Builder builder()
      Creates a new builder.
      Returns:
      Builder.
    • pageSize

      public int pageSize()
      Gets the page size (the number of entries that will be sent to the cluster in one network call).
      Returns:
      Page size.
    • perPartitionParallelOperations

      public int perPartitionParallelOperations()
      Gets the number of parallel operations per partition (how many in-flight requests can be active for a given partition).
      Returns:
      Per node parallel operations.
    • autoFlushInterval

      public int autoFlushInterval()
      Gets the auto flush interval, in milliseconds (the period of time after which the streamer will flush the per-node buffer even if it is not full).
      Returns:
      Auto flush interval.
    • retryLimit

      public int retryLimit()
      Gets the retry limit for a page. If a page fails to be sent to the cluster, the streamer will retry it a number of times. If all retries fail, the streamer will be aborted.
      Returns:
      Retry limit.
    • sameKeyUpdateMode

      public DataStreamerSameKeyUpdateMode sameKeyUpdateMode()
      Gets the mode controlling how same-key updates within one batch are handled.

      By default (DataStreamerSameKeyUpdateMode.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 DataStreamerSameKeyUpdateMode.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.

      Returns:
      Same-key update mode.