-
Notifications
You must be signed in to change notification settings - Fork 37
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
Add Source::Subscription
to identify the invocation comes from a subscription
#2305
Add Source::Subscription
to identify the invocation comes from a subscription
#2305
Conversation
This adds a new feature `experimental_feature_kafka_ingress_next` for a cluster of issues to tackle in subsequent PRs (notably restatedev#1423 and restatedev#964)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for creating this PR @slinkydeveloper. The changes look good to me. The one question I had was why PartitionProcessorRpcRequestId
becomes a ResourceId
. I imagined this id to be something internal that does not need to pay the price (additional overhead for evolvability) of being a ResourceId
.
@@ -45,6 +45,10 @@ pub struct IngressOptions { | |||
/// back to a previous version. | |||
#[cfg_attr(feature = "schemars", schemars(skip))] | |||
pub experimental_feature_enable_separate_ingress_role: bool, | |||
|
|||
/// Cluster of new features for the kafka ingress. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you gonna expand on what this cluster of new features are as you are tackling the other issues?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I put it in the commit. I won't put them in the code until i get them done 😄 Also check https://github.com/orgs/restatedev/projects/15/views/13?sliceBy%5Bvalue%5D=ingress_kafka
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. +1 for merging.
This is a leftover from the ingress PR of the past week.
I kept a generic name for the kafka ingress experimental feature, because I plan to bundle in there a bunch of other issue I plan to work on soon.