feat(new sink): add YDB sink support#25219
Open
1NepuNep1 wants to merge 18 commits intovectordotdev:masterfrom
Open
feat(new sink): add YDB sink support#252191NepuNep1 wants to merge 18 commits intovectordotdev:masterfrom
1NepuNep1 wants to merge 18 commits intovectordotdev:masterfrom
Conversation
feat(new sink): add YDB sink support
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
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
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.
Summary
This PR introduces a new YDB (Yandex Database) sink for Vector, enabling users to send log and trace data directly to YDB tables using the official
ydb-rs-sdk.Key features:
bulk_upsertfor high throughput,UPSERTfor indexed tables)YDB is a distributed SQL database with horizontal scalability and strong consistency, ideal for high-throughput log storage and real-time analytics.
Vector configuration
How did you test this PR?
Local Testing
cargo test --lib --features sinks-ydb ydb::make fmt,cargo clippy,make build-licensesmake generate-component-docs,CI=true make check-docs./scripts/check_changelog_fragments.shIntegration Testing
Tested against
ydbplatform/local-ydb:25.3Docker image with various table schemas (simple, indexed, NOT NULL constraints). Verified both insertion strategies, health checks, and schema refresh functionality.All integration tests configured for CI and passing.
Change Type
Is this a breaking change?
Does this PR include user facing changes?
no-changeloglabel to this PR.References
Notes
Known Limitations:
VRL Optional Values: Optional fields from VRL transforms are skipped with warning logs due to YDB SDK internal type representation. Does not affect normal operation.
Event Types: Supports
LogandTraceevents only.Metricevents are not supported.