Result type returned after deleting a stream.
Result type returned after deleting a stream.
The position of the write in the log
Maintains a full duplex connection to the EventStore
Maintains a full duplex connection to the EventStore
All operations are handled in a full async manner. Many threads can use an EsConnection at the same time or a single thread can make many asynchronous requests. To get the most performance out of the connection it is generally recommended to use it in this way.
OperationTimeoutException
OperationTimeoutException
Represents the settings for persistent subscription
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.
A client allowing to create, get the status and delete an existing projection.
The API miss documentation so I used the C# client as a starting point See : https://github.com/EventStore/EventStore/blob/release-v3.9.0/src/EventStore.ClientAPI/Projections/ProjectionsClient.cs
The API miss documentation so I used the C# client as a starting point See : https://github.com/EventStore/EventStore/blob/release-v3.9.0/src/EventStore.ClientAPI/Projections/ProjectionsClient.cs
IP & port of Event Store
The desired connection timeout
Maximum number of reconnections before backing off, -1 to reconnect forever
Delay before first reconnection
Maximum delay on reconnections
The UserCredentials to use for operations where other UserCredentials are not explicitly supplied.
The interval at which to send heartbeat messages.
The interval after which an unacknowledged heartbeat will cause the connection to be considered faulted and disconnect.
The maximum number of operation retries
The amount of time before an operation is considered to have timed out
Whether to resolve LinkTo events automatically
Whether or not to require Event Store to refuse serving read or write request if it is not master
Number of events to be retrieved by client as single message
The size of the buffer in element count
Strategy that is used when elements cannot fit inside the buffer
Url to access eventstore though the Http API
The number of serialization/deserialization functions to be run in parallel
Serialization done asynchronously and these futures may complete in any order, but results will be used with preserved order if set to true
Client identifier used to show a friendly name of client in Event Store.
Result type returned after writing to a stream.
Result type returned after writing to a stream.
The next expected version for the stream.
The position of the write in the log
System supported consumer strategies for use with persistent subscriptions.