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
Please describe the feature you are requesting.
As current DefaultMQPullConsumer is too atomic, the user needs to pay too much attention to the underlying layer when using the pullConsumer., so IMHO, it would be nice if can add a lite pull consumer for RocketMQ.
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
FEATURE REQUEST
Please describe the feature you are requesting.
As current DefaultMQPullConsumer is too atomic, the user needs to pay too much attention to the underlying layer when using the pullConsumer., so IMHO, it would be nice if can add a lite pull consumer for RocketMQ.
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
The text was updated successfully, but these errors were encountered: