summaryrefslogtreecommitdiff
path: root/README.rst
diff options
context:
space:
mode:
authorJeff Widman <jeff@jeffwidman.com>2018-11-17 02:53:08 -0800
committerJeff Widman <jeff@jeffwidman.com>2018-11-18 08:41:59 -0800
commit3eba52d65734da76858a5511aab19c6ed5e2bfe2 (patch)
tree55815d7d6628341db02026d6e90e668c2e0d39c8 /README.rst
parent09c1bcd7e27f2d59f3ba2a7a1e31a8eb82d27feb (diff)
downloadkafka-python-add-list-consumer-groups-offsets.tar.gz
Add list_consumer_group_offsets()add-list-consumer-groups-offsets
Support fetching the offsets of a consumer group. Note: As far as I can tell (the Java code is a little inscrutable), the Java AdminClient doesn't allow specifying the `coordinator_id` or the `partitions`. But I decided to include them because they provide a lot of additional flexibility: 1. allowing users to specify the partitions allows this method to be used even for older brokers that don't support the OffsetFetchRequest_v2 2. allowing users to specify the coordinator ID gives them a way to bypass a network round trip. This method will frequently be used for monitoring, and if you've got 1,000 consumer groups that are being monitored once a minute, that's ~1.5M requests a day that are unnecessarily duplicated as the coordinator doesn't change unless there's an error.
Diffstat (limited to 'README.rst')
0 files changed, 0 insertions, 0 deletions