1
1
kafka-python
2
2
############
3
3
4
- .. image :: https://img.shields.io/badge/kafka-0.10 %2C%200.9 %2C%200.8.2%2C%200.8.1 %2C%200.8-brightgreen.svg
4
+ .. image :: https://img.shields.io/badge/kafka-0.11 %2C%200.10 %2C%200.9 %2C%200.8-brightgreen.svg
5
5
:target: https://kafka-python.readthedocs.io/compatibility.html
6
6
.. image :: https://img.shields.io/pypi/pyversions/kafka-python.svg
7
7
:target: https://pypi.python.org/pypi/kafka-python
@@ -16,9 +16,9 @@ Python client for the Apache Kafka distributed stream processing system.
16
16
kafka-python is designed to function much like the official java client, with a
17
17
sprinkling of pythonic interfaces (e.g., consumer iterators).
18
18
19
- kafka-python is best used with newer brokers (0.10 or 0.9 ), but is backwards-compatible with
20
- older versions (to 0.8.0). Some features will only be enabled on newer brokers,
21
- however; for example, fully coordinated consumer groups -- i.e., dynamic
19
+ kafka-python is best used with newer brokers (0.9+ ), but is backwards-compatible with
20
+ older versions (to 0.8.0). Some features will only be enabled on newer brokers.
21
+ For example, fully coordinated consumer groups -- i.e., dynamic
22
22
partition assignment to multiple consumers in the same group -- requires use of
23
23
0.9 kafka brokers. Supporting this feature for earlier broker releases would
24
24
require writing and maintaining custom leadership election and membership /
@@ -136,7 +136,7 @@ for interacting with kafka brokers via the python repl. This is useful for
136
136
testing, probing, and general experimentation. The protocol support is
137
137
leveraged to enable a :meth: `~kafka.KafkaClient.check_version() `
138
138
method that probes a kafka broker and
139
- attempts to identify which version it is running (0.8.0 to 0.10 ).
139
+ attempts to identify which version it is running (0.8.0 to 0.11 ).
140
140
141
141
142
142
Low-level
0 commit comments