[Ingress] ingress-client crate
#3976
Open
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.
[Ingress]
ingress-clientcrateingress-clientimplements the runtime layer that receives ingress traffic, fans it out to the correct partition, and tracks completion. It exposes:Ingress, enforces inflight budgets, and resolves partition IDs before sending work downstream.IngestRecords, retries connections, and reports commit status to callers.ingress-coreonly ingests records and notify the caller once the record is "committed" to bifrost by the PP. This makes it useful to implement kafka ingress and other external ingestionStack created with Sapling. Best reviewed with ReviewStack.
Shuffler#4024IngressClientfor invocation and state mgmt #3980ingress-client#3975IngestRequestmessage #3974CommitTokenback from notify_committed() #3968ingress-clientcrate #3976