-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store caller information for background invokes #997
Comments
Open
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Dec 19, 2023
This commit introduces the Caller enum which each ServiceInvocation and InvocationMetadata carries along. The Caller captures who was the caller of the given service invocation. Currently Restate distinguishes between three values: * Caller::Ingress: Invocation originating from the ingress * Caller::Service: Invocation originating from a Restate service * Caller::Internal: Invocation originating from the Restate server to drive non-deterministic built-in services forward This fixes restatedev#997.
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Dec 19, 2023
This commit introduces the Caller enum which each ServiceInvocation and InvocationMetadata carries along. The Caller captures who was the caller of the given service invocation. Currently Restate distinguishes between three values: * Caller::Ingress: Invocation originating from the ingress * Caller::Service: Invocation originating from a Restate service * Caller::Internal: Invocation originating from the Restate server to drive non-deterministic built-in services forward This fixes restatedev#997.
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Dec 20, 2023
This commit introduces the Caller enum which each ServiceInvocation and InvocationMetadata carries along. The Caller captures who was the caller of the given service invocation. Currently Restate distinguishes between three values: * Caller::Ingress: Invocation originating from the ingress * Caller::Service: Invocation originating from a Restate service * Caller::Internal: Invocation originating from the Restate server to drive non-deterministic built-in services forward This fixes restatedev#997.
@tillrohrmann can you elaborate on why relying on response sink was not considered an option here? |
Because for background calls the response sink would be |
Uh sorry i completely forgot that, makes sense! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In order to also display for background invokes who was the caller, we should track this information in the runtime. I propose to not rely on the
ResponseSink
for extracting the caller information but to have a dedicated field for it.The text was updated successfully, but these errors were encountered: