Whether to resolve LinkTo events automatically
Where the subscription should start from, EventNumber
Whether or not in depth latency statistics should be tracked on this subscription.
The amount of time after which a message should be considered to be timedout and retried.
The maximum number of retries (due to timeout) before a message get considered to be parked
The size of the buffer listening to live messages as they happen
The number of events read at a time when paging in history
The number of events to cache when paging through history
The amount of time to try to checkpoint after
The minimum number of messages to checkpoint
maximum number of messages to checkpoint if this number is a reached a checkpoint will be forced.
The maximum number of subscribers allowed.
The ConsumerStrategy to use for distributing events to client consumers.
The amount of time to try to checkpoint after
The ConsumerStrategy to use for distributing events to client consumers.
Whether or not in depth latency statistics should be tracked on this subscription.
The number of events to cache when paging through history
The size of the buffer listening to live messages as they happen
maximum number of messages to checkpoint if this number is a reached a checkpoint will be forced.
The maximum number of retries (due to timeout) before a message get considered to be parked
The maximum number of subscribers allowed.
The amount of time after which a message should be considered to be timedout and retried.
The minimum number of messages to checkpoint
The number of events read at a time when paging in history
Whether to resolve LinkTo events automatically
Where the subscription should start from, EventNumber
Represents the settings for persistent subscription
You can use eventstore.j.PersistentSubscriptionSettingsBuilder) from Java
Whether to resolve LinkTo events automatically
Where the subscription should start from, EventNumber
Whether or not in depth latency statistics should be tracked on this subscription.
The amount of time after which a message should be considered to be timedout and retried.
The maximum number of retries (due to timeout) before a message get considered to be parked
The size of the buffer listening to live messages as they happen
The number of events read at a time when paging in history
The number of events to cache when paging through history
The amount of time to try to checkpoint after
The minimum number of messages to checkpoint
maximum number of messages to checkpoint if this number is a reached a checkpoint will be forced.
The maximum number of subscribers allowed.
The ConsumerStrategy to use for distributing events to client consumers.