rust(feat): SiftStreamAutoRegister — inline flow registration wrapper#618
Merged
Conversation
Adds SiftStreamAutoRegister<T> to sift_stream and SiftStreamAutoRegisterPy to sift_stream_bindings. Flows are registered with Sift automatically on first send. The FlowConfig is derived from the Flow's channel value types so callers need no upfront schema. Known flows can still be pre-registered via IngestionConfigForm to eliminate first-send latency. Subsequent sends for any registered flow are local cache-hits with no network overhead.
tsift
force-pushed
the
rust/sift-stream-auto-register
branch
from
4da23a7 to
18c49fc
Compare
marc-sift
requested changes
Jun 9, 2026
marc-sift
approved these changes
Jun 9, 2026
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
2 participants
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.
Adds
SiftStreamAutoRegister<T>to sift_stream andSiftStreamAutoRegisterPyto sift_stream_bindings.Flows are registered with Sift automatically on first send. If a
FlowConfigfor the flow was provided during construction of theSiftStreamAutoRegisterstruct, that will be used to register to theFlow. This allows providing types such as enums and bitarrays, as well as channel descriptions, units, and other metadata. Otherwise, a minimal config is generated based on the channel-name and type (the only available information at ingest time).Known flows can still be pre-registered via
IngestionConfigFormat init time to eliminate first-send latency. Subsequent sends for any registered flow are local cache-hits with no network overhead.