Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Not A Problem
-
None
-
None
-
None
-
None
Description
Is there a way to close the consumerIterator(stream), clean up the associated threads by doing a look up on the consumerGroupId? This would help in use cases where the consumption and sending happens in different threads with different protocols. And if the sending thread is shutdown, the sending thread might want to close the consumption thread.