delta/python-packages/kafka-python.git, branch add_new_api_versions github.com: mumrah/kafka-python.git Add API version determination code for newer kafka brokers 2020-03-19T18:15:21+00:00 Taras Voinarovskyi voyn1991@gmail.com 2020-03-19T18:15:21+00:00 8a72f1a567c4d71dc6a412f3d41ad80f56c495ed 






Add 2.1.1 to build_integration (#2019)
2020-03-16T16:30:02+00:00

Tincu Gabriel
gabi@aiven.io

2020-03-16T16:30:02+00:00

5d4b3ec4d6773740a036edb4103294a503a2a421












Fix docs by adding SASL mention
2020-03-02T16:58:53+00:00

Jeff Widman
jeff@jeffwidman.com

2020-03-02T16:58:53+00:00

34dc36d755abe6ec647efff74e284595497634ea

This was previously supported but wasn't documented.

Fix #1990.




This was previously supported but wasn't documented.

Fix #1990.






 Set length of header value to 0 if None
2020-03-02T16:52:04+00:00

kvfi
mail@ouafi.net

2020-02-24T13:21:30+00:00

d1dfb6dbf8ba108c1015ddb7245683dd946bd9ab












Bump version for development
2020-02-20T06:50:27+00:00

Dana Powers
dana.powers@gmail.com

2020-02-20T06:50:27+00:00

615b9e03b9a07381c8e382839c6f2772ec49586f












Patch Release 2.0.1
2020-02-20T06:23:02+00:00

Dana Powers
dana.powers@gmail.com

2020-02-20T06:23:02+00:00

fcc9a30c62662cee7aa2c1f69c0d06a9741e2700












KAFKA-8962: Use least_loaded_node() for describe_topics()
2020-02-16T22:54:06+00:00

Jeff Widman
jeff@jeffwidman.com

2020-02-16T18:11:32+00:00

3c3fdc11b555756c53ae63bfa46a915eab48f448

In KAFKA-8962 the `AdminClient.describe_topics()` call was changed from
using the controller to using the `least_loaded_node()`:
https://github.com/apache/kafka/commit/317089663cc7ff4fdfcba6ee434f455e8ae13acd#diff-6869b8fccf6b098cbcb0676e8ceb26a7R1540

As a result, no metadata request/response processing needs to happen
through the controller, so it's safe to remove the custom
error-checking. Besides, I don't think this error-checking even added
any value because AFAIK no metadata response would return a
`NotControllerError` because the recipient broker wouldn't realize the
metadata request was intended for only the controller.

Originally our admin client was implemented using the least-loaded-node,
then later updated to the controller. So updating it back to
least-loaded node is a simple case of reverting the associated commits.

This reverts commit 7195f0369c7dbe25aea2c3fed78d2b4f772d775b.

This reverts commit 6e2978edee9a06e9dbe60afcac226b27b83cbc74.

This reverts commit f92889af79db08ef26d89cb18bd48c7dd5080010.





In KAFKA-8962 the `AdminClient.describe_topics()` call was changed from
using the controller to using the `least_loaded_node()`:
https://github.com/apache/kafka/commit/317089663cc7ff4fdfcba6ee434f455e8ae13acd#diff-6869b8fccf6b098cbcb0676e8ceb26a7R1540

As a result, no metadata request/response processing needs to happen
through the controller, so it's safe to remove the custom
error-checking. Besides, I don't think this error-checking even added
any value because AFAIK no metadata response would return a
`NotControllerError` because the recipient broker wouldn't realize the
metadata request was intended for only the controller.

Originally our admin client was implemented using the least-loaded-node,
then later updated to the controller. So updating it back to
least-loaded node is a simple case of reverting the associated commits.

This reverts commit 7195f0369c7dbe25aea2c3fed78d2b4f772d775b.

This reverts commit 6e2978edee9a06e9dbe60afcac226b27b83cbc74.

This reverts commit f92889af79db08ef26d89cb18bd48c7dd5080010.







Fix topic error parsing in MetadataResponse
2020-02-16T06:32:30+00:00

Jeff Tribble
jtribble@newrelic.com

2020-02-11T22:22:15+00:00

7195f0369c7dbe25aea2c3fed78d2b4f772d775b












Bump version for development of next release
2020-02-11T06:34:59+00:00

Dana Powers
dana.powers@gmail.com

2020-02-11T06:34:59+00:00

bbb8c90391e446de81833bc38dba4233a781fa5b












Release 2.0.0
2020-02-11T05:57:38+00:00

Dana Powers
dana.powers@gmail.com

2020-02-11T05:57:38+00:00

ed8c9cb2d2ad0d9eb2b37a0bdc3cf01ca253b2b9