You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Today, it looks like the dapr go-sdk does not support the alpha-feature Bulk Subscribe described in the v1.11 Dapr docs. It would be great if the go-sdk supported bulk subscribe programmatically. Although the declarative setup is allegedly available (I am in the process of getting this to work...), it would be nice to have the same features as the .NET, Java, and JavaScript SDKs 😄.
Describe the solution you'd like
Support for Bulk Subscribe in the go-sdk
Ability to enable/disable, set maxMessageCount, and set maxAwaitDurationMs
Describe alternatives you've considered
Declarative setup is available, but not preferred by our team.
Additional context
I'm happy to provide any additional information if needed. I also took a look at the source code and couldn't find a way to bulk subscribe. Please correct me if i'm wrong!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Today, it looks like the dapr go-sdk does not support the alpha-feature Bulk Subscribe described in the v1.11 Dapr docs. It would be great if the go-sdk supported bulk subscribe programmatically. Although the declarative setup is allegedly available (I am in the process of getting this to work...), it would be nice to have the same features as the .NET, Java, and JavaScript SDKs 😄.
Describe the solution you'd like
enable
/disable, setmaxMessageCount
, and setmaxAwaitDurationMs
Describe alternatives you've considered
Declarative setup is available, but not preferred by our team.
Additional context
I'm happy to provide any additional information if needed. I also took a look at the source code and couldn't find a way to bulk subscribe. Please correct me if i'm wrong!
The text was updated successfully, but these errors were encountered: