Proto commits in EventStore/EventStore-Client-Dotnet

These 98 commits are when the Protocol Buffers files have changed:

2026-05-06

[release/v1.4] [DEV-1655] feat: support V2 projection engine on create (#412)

[DEV-1655] feat: support V2 projection engine on create (#411)

2026-05-05

feat: add appendRecords operation with consistency checks (#410) Co-authored-by: William Chong <william-chong@outlook.com>

feat: add appendRecords operation with consistency checks (#398)

2025-12-09

chore: use custom enum value (#377)

2025-10-22

[DEV-747] [DEV-839] [DEV-856] Implement Multi Stream Append (#363) * Implement Multi Stream Append

2025-10-10

Update protocols

2025-10-01

Adapt client to revised db feature changes

2025-09-30

Remove google proto files

status proto

2025-09-29

Checkpoint

2025-08-18

Remove unused proto files

2025-08-13

Add multistream append method

2025-08-11

refactor(projections): enhance error handling and projection options - Removed unnecessary comments from CoreErrorDetails messages. - Added FailedPrecondition error type to ErrorDetails. - Updated DeleteProjectionOptions to default DeleteEmittedStreams to true. - Refactored ProjectionsMapper methods for clarity and consistency. - Improved error handling in ProjectionsClient methods. - Added extension methods for ProjectionsClient to simplify usage.

Add multistream append method

2025-08-08

refactor: rename Shutdown method and related error types, and also refactored multiple projections methods - Updated method name from Shutdown to ShutdownServer for clarity. - Renamed ShutdownError to ShutdownServerError to reflect the new method name. - Adjusted related error handling in AdminClient and ErrorResults.

2025-08-07

refactor(massive): fix error model and delete zombie code - Consolidate persistent subscription related files by renaming for clarity - Update namespaces to reflect new organizational structure - Introduce new enums for projection modes and subsystem states - Adjust service names in proto files for consistency - Fixed v1 protocol service names - Refactored interceptors - Deleted zombie code

Add v2 protos and fix CI

2025-08-05

refactor(errors): rename model files and update exception handling - Renamed model files for consistency and clarity. - Updated exception handling to use KurrentException instead of KurrentClientException. - Added new error details for connectors and persistent subscriptions.

2025-08-04

feat(connectors): add ConnectorsService for managing connectors Implement ConnectorsService with methods for creating, reconfiguring, deleting, starting, stopping, and renaming connectors. This service provides a structured way to manage connector lifecycle and settings. Includes messages for handling connector operations and responses.

2025-08-01

refactor(proto): rename ServerFeatures to ServerFeaturesService for clarity

refactor(proto): update namespaces for persistent subscriptions and projections - Replace EventStore.Client references with KurrentDB.Protocol in multiple files - Clean up appsettings.json by removing unnecessary blank lines - Adjust formatting for consistency across various files

refactor(proto): rename services for consistency and clarity - Updated service names in operations.proto, streams.proto, and usermanagement.proto to follow a consistent naming convention. - Added C# namespaces for better organization in generated code. - Minor formatting adjustments for improved readability.

2025-07-30

THE PURGE HAS BEGUN

2025-07-29

Merge remote-tracking branch 'origin/schema-registry-reloaded' into schema-registry-reloaded

fix: stream state is now correctly reporteddeleted/tombstoned and stream not found

Add error handling for persistent subscriptions and introduce new error types

2025-07-28

[DEV-774] Admin and Scavenge operation tests (#360)

2025-07-16

Persistent subscription, Projection and User Management Mappings (#355)

2025-07-08

Sync with upstream

2025-07-07

feat(schema): add xunit runner configuration and improve validation methods - Introduced xunit.runner.json for test configuration. - Updated KurrentClientOptions validation methods for clarity. - Enhanced KurrentStreamsClient with additional type mappings. - Refactored test project files to ensure proper resource handling.

2025-07-03

Mapping for persistent subscriptions and user maangement

2025-06-30

Implement error handling in registry client using Result type (#352)

2025-06-23

[DEVEX-430] Implement new error details for registry client

2025-06-20

[DEVEX-429] Make data format mismatch a domain level exception

2025-06-18

Add missing compatibility modes in shared.proto

2025-06-17

Refactor metadata handling and error reporting; update MetadataDecoder and related classes for improved context management

2025-06-15

Remove legacy dynamic values, Result static methods, test utilities; add `IResultError` interface with extension methods

2025-06-12

Refactor namespaces and file structure for consistency; update error handling in Result classes Signed-off-by: Sérgio Silveira <sdsilveira@gmail.com>

2025-06-10

feat: implement multi stream append

2025-06-05

Game changing legacy call invoker implementation. Signed-off-by: Sérgio Silveira <sdsilveira@gmail.com>

2025-06-02

Refactor project structure and update namespaces for Kurrent.Client Signed-off-by: Sérgio Silveira <sdsilveira@gmail.com>

Completed core read, append. subscribe wrappers and removed unused interceptors, shims, and legacy models Deleted `ReportLeaderInterceptor`, compatibility shims (`Index`, `IsExternalInit`, `Range`, `TaskCompletionSource`), and outdated stream models (`AppendModel`, `DynamicProperties`). These components were redundant, outdated, or no longer relevant to the current implementation. Signed-off-by: Sérgio Silveira <sdsilveira@gmail.com>

2025-05-16

Remove obsolete gRPC and schema serialization components Deleted unused or outdated gRPC client-related code, schema serialization infrastructure, and related logic. Simplifies the codebase by discarding legacy components no longer in use or relevant.

2025-05-07

checkpoint

2025-05-02

Refactor stream handling and implement new append model Removed legacy stream handling code and replaced it with more modular, extensible append models using `OneOf` and Proto-based definitions. Introduced new `Appender` and `Protocol` utilities for improved batching, schema handling, and multi-stream transactional operations. Updated metadata processing strategy for compatibility with both old and new database contracts.

2025-05-01

Move and reorganize streams and protocol files into new modules. Refactored the folder structure for streams and protocol files to improve organization and clarity. Introduced `Modules` as the main folder for streams, and migrated protocol definitions to a new hierarchical structure under `proto/kurrentdb/protocol`. Added new v2 protocol files for schema registry functionality.

Rename namespaces and samples

The documentation is generated from this commit.

2025-04-30

Rename namespaces and samples

The documentation is generated from this commit.

2025-04-26

fixup

feat: supports new caught up and fell behind events.

2025-04-23

chore: [DEVEX-185] Rebranding (#326) * moved all files into EventStore.Client project * moved files into main project and deleted remaining empty projects dropped support for net6.0 and net7.0 added some helpers to fluentdocker playing around the idea of keeping the container on tests * Remove unused target frameworks and pass certificate in healthcheck * Tests * Rename test symbols * Test workflow * Testing something * More tests * Improve CI * Improve CI * Fixup * Publish actions * Temporarily disable Public actions * Fixup * Test warmup * [DEVEX-222] Add built-in auto-serialization (#329) * [DEVEX-222] Added configuration options for KurrentClientSettings Create method This should enable easier customisation like changing serializer settings. * [DEVEX-222] Added overloads of Append methods that take regular events They currently use dummy serialisation * [DEVEX-222] Added TryDeserialize method to ResolvedEvent Currently it's implemented in a dummy way * [DEVEX-222] Added first working, but not yet complete JSON built-in serialization It's not fully ready, as it has hardcoded schema serializer. Main question will be how much from schema registry I need to move here. * [DEVEX-222] Added autoserialization settings and removed serializer from ResolvedEvent Per @RagingKore suggestion it'll be better not to keep the reference to serializer in ResolvedEvent to keep the clear intention behind it. Now, the serializer is resolved from schema registry based on the auto-serialization settings. Made possible to register more than one serializer per content type. Currently it doesn't support more schema definition types. To be discussed how to include them later on. * [DEVEX-222] Made serialization settings to create specific serializers That will make resolution easier and give users ability to inject their own serializers implementation * [DEVEX-222] Added override of the serialization settings to Persistent Subscriptions * [DEVEX-222] Added serialization type and merged serialization into Serialization Context Previously we had DeserializationContext, but after consideration, it'll be better to merge those concepts to make easier customizations per operations (e.g. append, subscribe, etc.). * [DEVEX-222] Added message type name resolution strategy Refactored the code accordingly. It takes the full object instead of the limited number of parameters, as you may be using metadata to get parameters about clrtype. * [DEVEX-222] Refactored Event Type Mapper to not be responsible for resolution of CLR types * [DEVEX-222] Added automatic message clr type resolution * [DEVEX-222] Added metadata extensions to allow injecting type informations * [DEVEX-222] Made CLR type be resolved based on the message type metadata header * [DEVEX-222] Added the MessageTypeResolutionStrategyWrapper for caching resolved types * [DEVEX-222] Added MessageSerializationContext to pass additional information like category name * [DEVEX-222] Refactored SerializationContext into MessageSerializerWrapper to make clearer responsibilities Actually, it's just wrapping message serializer based on the client settings. * [DEVEX-222] Added message type maps registration * [DEVEX-222] Added helpers for custom type resolutions strategy Removed also obsolete SerializationSettings * [DEVEX-222] Replaced MessageSerializerWrapper usage with more generic IMessageSerializer There's no need to force all code to know about wrapper existence, it's okay to just create it during the setup. * [DEVEX-222] Made Message to be record instead of Struct * [DEVEX-222] Refactored new AppendToStreamAsync method to have simplified syntax Now they don't require all the fancy, but redundant in most cases Stream Positions, Directions, EventData etc. * [DEVEX-222] Refactored Reading events signatures to use options instead of parameters Thanks to that safe defaults are already provided * [DEVEX-222] Renamed MessageTypeResolutionStrategy to MessageTypeNamingStrategy * [DEVEX-222] Made old Read methods be wrapper of the new one, instead the other way round * [DEVEX-222] Added serialization configuration overrides Old append and read methods won't be doing default serialization by default. The new one will use auto-seriailization and allow to customize or disable it. * [DEVEX-222] Removed storing CLR type in metadata and moved it to message type name Now the FullTypeName is placed in the event type name. Not perfect but here it is. * [DEVEX-222] Added possibility to register types for category name Thanks to that they will be resolved automatically by the registered convention. Then user doesn't need to provide the string name by hand. Added MessageTypeNamingResolution context besides the MessageSerializationContext as it's orthogonal and just overlapping context. * [DEVEX-222] Added SubscribeToAllOptions and Subscription Listener This is a similar API as we already have in Java client, to simplify the handlers registration. * [DEVEX-222] Addes SubscribeToStreamOptions and applied it accordingly to subscirbe to all changes * [DEVEX-222] Renamed DeserializedEvent to Message in ResolvedEvent I think that in the longer term, this will make intention clearer * [DEVEX-222] Added persistent subscription litener and capability to customize serialization for Persistent Subscriptions * [DEVEX-222] Extended Serialization tests for Appends and Reads * [DEVEX-222] Added capability to automatically deserialize message metadata By default it'll try to resolve the TraceMetadata, it can be override with the general type or using custom resolution strategy. * [DEVEX-222] For unknown reason the reverse Enumerable.Reverse wasn't taken but Array.Reverse 🤷 * [DEVEX-222] Fixed type resolution to correclty find types by assembly * [DEVEX-222] Added tests for serialization compatibility between manual and automatic deserialization * [DEVEX-222] Added tests for appends with autoserialization * Revert "[DEVEX-222] Added tests for appends with autoserialization" This reverts commit 04e068554a0a8510af7da0b1e5b035edf513e679. I'm reverting it as old methods are wrappers for new ones, so the test scenarios are covered by the old test suite. * [DEVEX-222] Extended serialization test suite * [DEVEX-222] Added tests for auto-serialization in Catch-up subscriptions * [DEVEX-222] Added tests for auto-serialization in persistent subscriptions * [DEVEX-222] Added Expected prefix to StreamState and StreamRevision in AppendToStreamOptions * [DEVEX-222] Merged namespaces Fixed also XML docs comments * [DEVEX-222] Renamed NulloMessageSerializer to NullMesageSerializer * [DEVEX-222] Added AppendToStream methods that has expected stream revision as a parameter * [DEVEX-222] Added XML documentation for Serialization settings * [DEVEX-222] Added Unit tests * [DEVEX-222] Added tests for type resolution Used also two external assemlies - one that's loaded, - one that's never loaded. To double-check behaviour of loading types from different assemblies. * [DEVEX-222] Added SchemaRegistry tests * Revert "[DEVEX-222] Add built-in auto-serialization (#329)" (#332) This reverts commit 44607ea8381974c5fa6a903fa3b34101825d3036. * [DEVEX-222] Add built-in auto-serialization (#333) * [DEVEX-222] Added configuration options for KurrentClientSettings Create method This should enable easier customisation like changing serializer settings. * [DEVEX-222] Added overloads of Append methods that take regular events They currently use dummy serialisation * [DEVEX-222] Added TryDeserialize method to ResolvedEvent Currently it's implemented in a dummy way * [DEVEX-222] Added first working, but not yet complete JSON built-in serialization It's not fully ready, as it has hardcoded schema serializer. Main question will be how much from schema registry I need to move here. * [DEVEX-222] Added autoserialization settings and removed serializer from ResolvedEvent Per @RagingKore suggestion it'll be better not to keep the reference to serializer in ResolvedEvent to keep the clear intention behind it. Now, the serializer is resolved from schema registry based on the auto-serialization settings. Made possible to register more than one serializer per content type. Currently it doesn't support more schema definition types. To be discussed how to include them later on. * [DEVEX-222] Made serialization settings to create specific serializers That will make resolution easier and give users ability to inject their own serializers implementation * [DEVEX-222] Added override of the serialization settings to Persistent Subscriptions * [DEVEX-222] Added serialization type and merged serialization into Serialization Context Previously we had DeserializationContext, but after consideration, it'll be better to merge those concepts to make easier customizations per operations (e.g. append, subscribe, etc.). * [DEVEX-222] Added message type name resolution strategy Refactored the code accordingly. It takes the full object instead of the limited number of parameters, as you may be using metadata to get parameters about clrtype. * [DEVEX-222] Refactored Event Type Mapper to not be responsible for resolution of CLR types * [DEVEX-222] Added automatic message clr type resolution * [DEVEX-222] Added metadata extensions to allow injecting type informations * [DEVEX-222] Made CLR type be resolved based on the message type metadata header * [DEVEX-222] Added the MessageTypeResolutionStrategyWrapper for caching resolved types * [DEVEX-222] Added MessageSerializationContext to pass additional information like category name * [DEVEX-222] Refactored SerializationContext into MessageSerializerWrapper to make clearer responsibilities Actually, it's just wrapping message serializer based on the client settings. * [DEVEX-222] Added message type maps registration * [DEVEX-222] Added helpers for custom type resolutions strategy Removed also obsolete SerializationSettings * [DEVEX-222] Replaced MessageSerializerWrapper usage with more generic IMessageSerializer There's no need to force all code to know about wrapper existence, it's okay to just create it during the setup. * [DEVEX-222] Made Message to be record instead of Struct * [DEVEX-222] Refactored new AppendToStreamAsync method to have simplified syntax Now they don't require all the fancy, but redundant in most cases Stream Positions, Directions, EventData etc. * [DEVEX-222] Refactored Reading events signatures to use options instead of parameters Thanks to that safe defaults are already provided * [DEVEX-222] Renamed MessageTypeResolutionStrategy to MessageTypeNamingStrategy * [DEVEX-222] Made old Read methods be wrapper of the new one, instead the other way round * [DEVEX-222] Added serialization configuration overrides Old append and read methods won't be doing default serialization by default. The new one will use auto-seriailization and allow to customize or disable it. * [DEVEX-222] Removed storing CLR type in metadata and moved it to message type name Now the FullTypeName is placed in the event type name. Not perfect but here it is. * [DEVEX-222] Added possibility to register types for category name Thanks to that they will be resolved automatically by the registered convention. Then user doesn't need to provide the string name by hand. Added MessageTypeNamingResolution context besides the MessageSerializationContext as it's orthogonal and just overlapping context. * [DEVEX-222] Added SubscribeToAllOptions and Subscription Listener This is a similar API as we already have in Java client, to simplify the handlers registration. * [DEVEX-222] Addes SubscribeToStreamOptions and applied it accordingly to subscirbe to all changes * [DEVEX-222] Renamed DeserializedEvent to Message in ResolvedEvent I think that in the longer term, this will make intention clearer * [DEVEX-222] Added persistent subscription litener and capability to customize serialization for Persistent Subscriptions * [DEVEX-222] Extended Serialization tests for Appends and Reads * [DEVEX-222] Added capability to automatically deserialize message metadata By default it'll try to resolve the TraceMetadata, it can be override with the general type or using custom resolution strategy. * [DEVEX-222] For unknown reason the reverse Enumerable.Reverse wasn't taken but Array.Reverse 🤷 * [DEVEX-222] Fixed type resolution to correclty find types by assembly * [DEVEX-222] Added tests for serialization compatibility between manual and automatic deserialization * [DEVEX-222] Added tests for appends with autoserialization * Revert "[DEVEX-222] Added tests for appends with autoserialization" This reverts commit 04e068554a0a8510af7da0b1e5b035edf513e679. I'm reverting it as old methods are wrappers for new ones, so the test scenarios are covered by the old test suite. * [DEVEX-222] Extended serialization test suite * [DEVEX-222] Added tests for auto-serialization in Catch-up subscriptions * [DEVEX-222] Added tests for auto-serialization in persistent subscriptions * [DEVEX-222] Added Expected prefix to StreamState and StreamRevision in AppendToStreamOptions * [DEVEX-222] Merged namespaces Fixed also XML docs comments * [DEVEX-222] Renamed NulloMessageSerializer to NullMesageSerializer * [DEVEX-222] Added AppendToStream methods that has expected stream revision as a parameter * [DEVEX-222] Added XML documentation for Serialization settings * [DEVEX-222] Added Unit tests * [DEVEX-222] Added tests for type resolution Used also two external assemlies - one that's loaded, - one that's never loaded. To double-check behaviour of loading types from different assemblies. * [DEVEX-222] Added SchemaRegistry tests --------- Co-authored-by: Oskar Dudycz <oskar.dudycz@eventstore.com> * Rename namespaces (#335) * Rename namespaces * feat: add ability to manually dispatch publish workflow * chore: set tag prefix to `kurrent@` * chore: set minimum-major-minor to 1.0 * chore: change name to `Kurrent Inc` * disable minver * refactor: move ExpectedRevision to StreamState. (#337) * [DEVEX-185] Removed leftover folders that had KurrentDb instead of KurrentDB (#340) It seems that after conflicts when merging StreamRevision PR, the code before merging stayed as duplicated without capital B in KurrentDb. I checked by doing copying with override from those folders to the proper one, and there were no differences besides those stream revision changes, so it's safe to just remove them. * chore: update license and readme * [DEVEX-222] - Auto serialization feedback improvements (#338) * [DEVEX-222] Fixed the missing application of custom serialization setting in AppendToStreamAsync method * [DEVEX-222] Added stream state as a mandatory parameter in append to stream Added also override for raw event append that has options and made other methods obsolete. Introduced OperationOptions that compose default client operation settings plus credentials and deadlines. * [DEVEX-222] Ensured that metadata is serialized with auto-serialization as regular system metadata * [DEVEX-222] Adjusted samples to match the append api changes Added also factor for event data that's not requiring to provide id immediately * [DEVEX-222] Added MessageData type as an easier to use replacement for EventData, and better aligned with general usage of messages instead of just events * [DEVEX-222] Refactored setting stream metadata to use OperationOptions * [DEVEX-222] Added DeserializedData and DeserializedMessages extensions for read results That should be a middle ground without forcing people to use a regular ResolvedEvent if they don't want to * [DEVEX-222] Simplified the message serializer implementation Now serializer creates a derived serializer merging operation settings with default settings if needed. That allowed to hide internal details and there's no need to pass content type explicitly, as it's already in settings. Extended SchemaRegistry to provide wrapper methods to naming resolution context. Thanks to that MessageSerializer doesn't need to reference it internally. To make responsibilities clearer made also naming resolution context part of serializer context. * [DEVEX-222] Marked old Stream Metadata options as obsolete * [DEVEX-222] Made old Read methods obsolete and used the new ones in tests * [DEVEX-222] Made Read options nullable, to precisely know if user provided options or not * [DEVEX-222] Made the Read Options nullable and thanks to that smarter, so e.g. FromEnd assigns also backwards if it wasn't set * [DEVEX-222] Made old SetStreamMetadata and ConditionalAppend methods obsolete * [DEVEX-222] Added delete method with options * [DEVEX-222] Made old subscription methods obsolete and adjusted tests to use them * [DEVEX-222] Added Tombstone method with options and made the old obsolete * [DEVEX-222] Made all persistent subscription methods obsolete * [DEVEX-222] Added samples showcasing auto-serialization usage * [DEVEX-222] Reshaped type resolution strategy to take EventRecord instead of just raw string. That should enable current users to override their strategy if they used something more than just message type name from EventRecord. It needs to be EventRecord and not ResolvedEvent, as resolution happens before creating ResolvedEvent. * [DEVEX-222] Changed message type registration to allow multiple message type names mapping to the same CLR class * [DEVEX-222] Nested Message type mapping into settings object * [DEVEX-222] Added nested message type mapping * [DEVEX-222] Replaced clr type with clr type name in naming resolution Tha makes naming strategy focused on just mapping types back and forth and allowing to disable auto registration * chore: point workflows to kurrent-io docker images --------- Co-authored-by: William Chong <william-chong@outlook.com> Co-authored-by: Oskar Dudycz <oskar.dudycz@eventstore.com> Co-authored-by: Yo Eight <yo.eight@gmail.com> Co-authored-by: Oskar Dudycz <oskar.dudycz@gmail.com> Co-authored-by: Jason Mitchell <jasonmitchell@live.co.uk>

The documentation is generated from this commit.

2025-04-21

wip

2025-04-10

wip

2025-03-24

[DEVEX-185] Removed leftover folders that had KurrentDb instead of KurrentDB (#340) It seems that after conflicts when merging StreamRevision PR, the code before merging stayed as duplicated without capital B in KurrentDb. I checked by doing copying with override from those folders to the proper one, and there were no differences besides those stream revision changes, so it's safe to just remove them.

The documentation is generated from this commit.

2025-03-04

Rename namespaces (#335) * Rename namespaces

2025-01-08

Publish actions

2025-01-07

Rename test symbols

2024-12-18

moved files into main project and deleted remaining empty projects dropped support for net6.0 and net7.0 added some helpers to fluentdocker playing around the idea of keeping the container on tests

2024-12-16

moved all files into EventStore.Client project

2024-04-26

DEV-297 - Add tracing instrumentation of Append & Subscribe operations (#294)

2024-02-28

Subscriptions Without Callbacks (DEV-112) (#282) * add sensible subscriptions * add sensible persistent subscriptions * obsolete old subscription / ps apis * put missing props on sever exception in net48

2024-01-29

Add missing options in create projection

2023-08-09

live caught up control message for subscription

2022-12-23

Update persistent subscriptions to minimum viable tier

2022-01-18

implement server capabilities - ensure calls are disposed - rediscovery on server not available - client reusable after discovery or server caps failure Co-authored-by: Timothy Coleman <timothy.coleman@gmail.com>

2021-11-11

pipe server messages through channel first

2021-07-08

implement bidi append

2021-06-28

implement bidi append

2021-06-08

Add filtered persistent subscriptions (#122)

2021-05-06

Implement persistent subscriptions to $all: (#108) Update persistent subscriptions proto file Make StreamPosition and Position implement new interface: IPosition Convert `StreamPosition StartFrom` to `IPosition? StartFrom` in PersistentSubscriptionSettings Move SystemStreams.cs from src/EventStore.Client.Streams to src/EventStore.Client and add the $all stream Move SystemMetadata class to a separate file in the EventStore.Client.Streams project Added: Create persistent subscriptions to $all Added: Update persistent subscriptions to $all Added: Delete persistent subscriptions to $all Added: Read from persistent subscriptions to $all Delete no longer valid test: create_on_all_stream.the_completion_fails_with_invalid_stream Update existing tests to use SystemStreams.AllStream/SystemRoles.All instead of "$all" Move all persistent subscription to stream tests to SubscriptionToStream directory Move stream persistent subscription tests to EventStore.Client.SubscriptionToStream namespace Added tests: create persistent subscriptions to $all Added tests: update persistent subscriptions to $all Added tests: delete persistent subscriptions to $all Added tests: connect to persistent subscriptions to $all Added tests: ACK/NAK for persistent subscriptions to $all Add the following wrappers to the persistent subscription client: CreateToAllAsync, DeleteToAllAsync, UpdateToAllAsync, SubscribeToAllAsync Update tests to use wrappers: CreateToAllAsync, DeleteToAllAsync, UpdateToAllAsync, SubscribeToAllAsync

2020-09-23

update proto

2020-09-19

added missing field in proto

2020-08-26

ensuring backwards compatibility

2020-08-05

Add restarting persistent subscriptions

2020-06-08

Changed: Restructured stream name for future planned changes

2020-06-01

Do gossip requests over gRPC Update VNodeState enum to match server and add unused values to notAllowedStates

2020-05-11

Provide a read status which will allow the client to avoid exceptions

2020-05-08

wip

Introduce the ability for the consumer to decide to throw on failure This behaviour is currently only applied when performing a write.

2020-04-24

Add operations proto contract and implementation Add the following to client.Operations: - MergeIndexes - Shutdown - ResignNode - SetNodePriority Add RestartSubsystem to client.ProjectionManagement

2020-04-02

reorganize solution - spin up a container per test fixture as we can no longer run the server in process - turn on nulability - split each proto into its own project - move tests to different folder

2020-03-24

initial commit

2020-03-05

gossip over gRPC: - Add flags internal_tcp_uses_tls and external_tcp_uses_tls to cluster.proto - Set the internal/external secure/non-secure endpoints depending on the value of the flags

2020-02-24

Split out gossip and elections services in proto.

use snake case in cluster proto.

Internal gossip and elections over gRPC - Add proto definition for internal gossip and elections - Add a Cluster gRPC service and client - Add a cluster client cache to allow channel reuse - Remove ElectController and Post for the GossipController - Don't run GossipController over internal http

2020-02-18

Consolidate Protos (#2291) * use shared proto * use better terminology

2020-02-17

windoze

2020-02-12

use internal subscriptions model in grpc stream subscriptions

2020-01-22

use int64 for time consistently

2020-01-16

Align names of projects, packages and classes

2020-01-14

Respect `maxCount` when reading from `$all`

2020-01-13

implementation of scavenge database in grpc

2020-01-08

Allow Clients to Specify Which UUID Type They Want

2020-01-02

make all plural -> singlar in proto oneof

2019-12-11

Protobuf Contract Improvements (#2102) * Making End explicit on Reads * Zero Allocation UUID implementation

2019-12-05

GRPC Client and Server (#2012) - move solution to dotnet core 3.1 - async await most tests - kestrel http service - GRPC Implementation of Streams API - GRPC implementation of persistent subscriptions - GRPC implementation of projections management api - GRPC implementation of user management - Acceptance Tests for Client API