Schema Registry #357
Draft
Schema Registry #357
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dropped support for net6.0 and net7.0 added some helpers to fluentdocker playing around the idea of keeping the container on tests
…et into DEVEX-185-Rebranding
…et into DEVEX-185-Rebranding
Co-authored-by: Yorick Laupa <yo.eight@gmail.com>
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.
Moved core files and modules to reorganized namespaces for better project modularity and maintainability. Introduced a clearer folder structure aligning with version-specific implementations, while consolidating and relocating common utility files.
`DefaultRequestVersionHandler` was removed to simplify or deprecate its functionality. Additionally, the namespaces were updated to adopt a cleaner, concise syntax throughout the project for improved readability and consistency.
Removed redundant `using` directives and simplified several class constructors. Streamlined method signatures and adhered to consistent formatting across interceptors. Introduced `KurrentDBConnectionString` for parsing and managing connection strings, along with updated connectivity settings implementation in `KurrentDBClientConnectivitySettings`.
…otobuf. Added abstractions and implementations for schema serialization and deserialization, enabling multi-format data handling. Included support for schema-based data validation, serialization exceptions, and extensibility for future formats. Refactored client modules to integrate the schema framework seamlessly.
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.
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.
Refactored schema serialization to use a streamlined auto-registration and validation approach. Introduced new exception types to improve error specificity, added gRPC compression support (e.g., Brotli), and improved hash code generation APIs. Replaced legacy serialization code, cleaned up unused methods, and aligned serialization formats with updated schema registry standards.
- Renamed several files for consistency and clarity. - Updated project references in multiple .csproj files. - Refactored KurrentClientOptions and related classes for improved structure.
…ethods - 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.
…t into schema-registry-reloaded
w1am
force-pushed
the
schema-registry-reloaded
branch
10 times, most recently
from
87331af to
189ce5b
Compare
w1am
force-pushed
the
schema-registry-reloaded
branch
10 times, most recently
from
bb499f7 to
c933253
Compare
* Add the authorization header at the interceptor level instead of the call level * Fix assertions in user management
w1am
force-pushed
the
schema-registry-reloaded
branch
from
c933253 to
abbd002
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.