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.
The addition of the ability to subscribe to multiple topics in v1.4.0 of this interface, however the unsubscribe functionality is asymmetric to this allowing for subscriptions from all topics to be completed only.
Describe the solution you'd like
The underlying functionality which controls unsubscriptions within the current api calls the librdkafka function rd_kafka_unsubscribe to achieve unsubscriptions. This is essentially the same as calling subscribe with no topics which doesn't provide sufficient granularity.
Describe alternatives you've considered
Exposure of the assignment interface appears to allow a level of granularity that would begin to allow this to be achieved. This allows a user to remove the consumption of data from particular topic/partition pairs and could form the basis for a solution.
Additional resource
Prototypes for the C code which may be useful for exposure of the Assignment function calls are available here
The text was updated successfully, but these errors were encountered:
consume_start/stop is not feasible because index of a topic is not visible for consumer unless the topic is created in the same process. So the deleting the assignment might be the only way to do this.
Internal Feature Request
Is your feature request related to a problem? Please describe.
The addition of the ability to subscribe to multiple topics in v1.4.0 of this interface, however the unsubscribe functionality is asymmetric to this allowing for subscriptions from all topics to be completed only.
Describe the solution you'd like
The underlying functionality which controls unsubscriptions within the current api calls the librdkafka function
rd_kafka_unsubscribe
to achieve unsubscriptions. This is essentially the same as calling subscribe with no topics which doesn't provide sufficient granularity.This is outlined here.
Describe alternatives you've considered
Exposure of the assignment interface appears to allow a level of granularity that would begin to allow this to be achieved. This allows a user to remove the consumption of data from particular topic/partition pairs and could form the basis for a solution.
Additional resource
Prototypes for the C code which may be useful for exposure of the Assignment function calls are available here
The text was updated successfully, but these errors were encountered: