package kurrentdb.protocol.v2.streams.errors

Get desktop application:
View/edit binary Protocol Buffers messages

Details for APPEND_CONSISTENCY_VIOLATION errors. Contains all consistency checks that were violated during the append operation. Only violated checks are included; satisfied checks are omitted.

• repeated ConsistencyViolation violations = 1

  The consistency checks that were violated.

Details for APPEND_RECORD_SIZE_EXCEEDED errors.

• string stream = 1

  The name of the stream where the append was attempted.

• string record_id = 2

  The identifier of the record that exceeded the size limit.

• int32 size = 3

  The actual size of the record in bytes.

• int32 max_size = 4

  The maximum allowed size of a single record in bytes.

Details for APPEND_TRANSACTION_SIZE_EXCEEDED errors.

• int32 size = 1

  The actual size of the transaction in bytes.

• int32 max_size = 2

  The maximum allowed size of an append transaction in bytes.

Details for a single consistency check that was violated.

Used in: AppendConsistencyViolationErrorDetails

• int32 check_index = 1

  Index of the check in the original consistency_checks list.

• oneof type

  • ConsistencyViolation.StreamStateViolation stream_state = 2

    The stream was not at the expected state.

A stream state check was violated because the actual state did not match the expected state. The actual_state field reports the stream's observed state: >= 0 : The stream exists and is at this revision -1 : The stream does not exist (NO_STREAM) -5 : The stream has been soft-deleted (DELETED) -6 : The stream has been tombstoned (TOMBSTONED) Notes: - ANY (-2) and EXISTS (-4) are never returned as actual_state values. - When a stream exists, the server returns the actual revision number (>= 0).

Used in: ConsistencyViolation

• string stream = 1

  The name of the stream whose state was checked.

• sint64 expected_state = 2

  The expected state of the stream as specified in the consistency check. Non-negative values (>= 0) are real revision numbers. Negative values are RevisionConstants sentinels: -2 (ANY), -4 (EXISTS), -1 (NO_STREAM), -5 (DELETED), -6 (TOMBSTONED).

• sint64 actual_state = 3

  The actual state of the stream at the time the check was evaluated. Non-negative values (>= 0) are real revision numbers. Negative values are RevisionConstants sentinels: -1 (NO_STREAM), -5 (DELETED), -6 (TOMBSTONED).

Details for STREAM_ALREADY_EXISTS errors.

• string stream = 1

  The name of the stream that already exists.

Details for STREAM_ALREADY_IN_APPEND_SESSION errors.

• string stream = 1

  The name of the stream that appears multiple times.

Details for STREAM_DELETED errors.

• string stream = 1

  The name of the stream that was deleted.

Details for STREAM_NOT_FOUND errors.

• string stream = 1

  The name of the stream that was not found.

Details for STREAM_REVISION_CONFLICT errors.

• string stream = 1

  The name of the stream that had a revision conflict.

• sint64 expected_revision = 2

  The expected revision that was provided in the append request.

• sint64 actual_revision = 3

  The actual current revision of the stream.

Details for STREAM_TOMBSTONED errors.

• string stream = 1

  The name of the stream that was tombstoned.

Error codes specific to the Streams API. These errors represent failure modes when working with streams of records.

• STREAMS_ERROR_UNSPECIFIED = 0

  Default value. This value is not used. An error code MUST always be set to a non-zero value. If an error code is not explicitly set, it MUST be treated as an internal server error (INTERNAL).

• STREAMS_ERROR_STREAM_NOT_FOUND = 1

  The requested stream does not exist in the database. Common causes: - Stream name typo or incorrect stream identifier - Stream was never created (no events appended yet) - Stream was deleted and not yet recreated Client action: Verify the stream name is correct. Create the stream by appending to it. Recoverable by creating the stream first (append with NO_STREAM expected revision).

• STREAMS_ERROR_STREAM_ALREADY_EXISTS = 2

  The stream already exists when an operation expected it not to exist. Common causes: - Attempting to create a stream that already has events - Using NO_STREAM expected revision on an existing stream - Race condition with concurrent stream creation Client action: Use the existing stream or use a different expected revision. Recoverable by adjusting the expected revision or using the existing stream.

• STREAMS_ERROR_STREAM_DELETED = 3

  The stream has been soft deleted. Soft-deleted streams are hidden from stream lists but can be restored by appending to them. Common causes: - Stream was explicitly soft-deleted via delete operation - Attempting to read from a soft-deleted stream Client action: Restore the stream by appending new events, or accept that the stream is deleted. Recoverable by appending to the stream to restore it.

• STREAMS_ERROR_STREAM_TOMBSTONED = 4

  The stream has been tombstoned (permanently deleted). Tombstoned streams cannot be restored and will never accept new events. Common causes: - Stream was explicitly tombstoned via tombstone operation - Administrative deletion of sensitive data - Attempting to write to or read from a tombstoned stream Client action: Stream is permanently removed. Create a new stream with a different name if needed. Not recoverable - the stream cannot be restored.

• STREAMS_ERROR_STREAM_REVISION_CONFLICT = 5

  The expected revision does not match the actual stream revision. This is an optimistic concurrency control failure. Common causes: - Another client modified the stream concurrently - Client has stale state about the stream revision - Race condition in distributed system Client action: Fetch the current stream revision and retry with the correct expected revision. Recoverable by reading the current state and retrying with proper optimistic concurrency control.

• STREAMS_ERROR_APPEND_RECORD_SIZE_EXCEEDED = 6

  A single record being appended exceeds the maximum allowed size. Common causes: - Record payload is too large (exceeds server's max record size configuration) - Excessive metadata in properties - Large binary data without chunking Client action: Reduce record size, split large payloads across multiple records, or increase server limits. Recoverable by reducing record size or adjusting server configuration.

• STREAMS_ERROR_APPEND_TRANSACTION_SIZE_EXCEEDED = 7

  The total size of all records in a single append session exceeds the maximum allowed transaction size. Common causes: - Too many records in a single append session - Combined payload size exceeds server's max transaction size - Attempting to write very large batches Client action: Split the append into multiple smaller transactions. Recoverable by reducing the number of records per append session.

• STREAMS_ERROR_STREAM_ALREADY_IN_APPEND_SESSION = 8

  The same stream appears multiple times in a single append session. This is currently not supported to prevent complexity with expected revisions and ordering. Common causes: - Accidentally appending to the same stream twice in one session - Application logic error in batch operations Client action: Remove duplicate streams from the append session or split into multiple sessions. Recoverable by restructuring the append session to reference each stream only once.

• STREAMS_ERROR_APPEND_SESSION_NO_REQUESTS = 9

  An append session was started but no append requests were sent before completing the stream. Common causes: - Client completed the stream without sending any AppendRequest messages - Application logic error Client action: Ensure at least one AppendRequest is sent before completing the stream. Recoverable by properly implementing the append session protocol.

• STREAMS_ERROR_APPEND_CONSISTENCY_VIOLATION = 14

  One or more consistency checks failed during an AppendRecords operation. The transaction is aborted — no records are written. Each check in the request is evaluated before commit. A check can be: - A stream state check: the stream must be at a specific revision or lifecycle state - A query predicate: a server-side expression that must evaluate to true Common causes: - A stream state check found the stream at a different revision than expected - A stream referenced in a state check does not exist, was deleted, or was tombstoned - A query predicate evaluated to false Client action: Inspect the AppendConsistencyViolationErrorDetails to determine which checks failed and why, then correct the request or refresh local state and retry. Recoverable by reading the current state and resubmitting with updated checks.