Updating Python SDK with new Rust core version#19
Merged
elenagaljak-db merged 9 commits intomainfrom Feb 12, 2026
Merged
Conversation
teodordelibasic-db
previously approved these changes
Feb 5, 2026
Contributor
teodordelibasic-db
left a comment
There was a problem hiding this comment.
Looks quite good, I think we should just mention a few breaking changes.
6d8232f to
09eacd5
Compare
Signed-off-by: elenagaljak-db <elena.galjak@databricks.com>
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.
What changes are proposed in this pull request?
WHAT:
sync_wrapper.rs,async_wrapper.rs,common.rs,auth.rs) that expose thecore Rust SDK functionality to Python
TableProperties,StreamConfigurationOptions,RecordType,AckCallback,HeadersProviderWHY:
The previous Python SDK duplicated logic from the Rust SDK, creating maintenance overhead and potential
inconsistencies. By wrapping the Rust SDK directly, we get:
The Python API remains unchanged for end users, ensuring a smooth migration path.
Local benchmark results:
ingest_record_offset
ingest_record_no_wait
pure python:
How is this tested?
ingest_recordmethodTablePropertiesaccepts protobuf descriptor objects as before