summaryrefslogtreecommitdiff
path: root/kafka/errors.py
Commit message (Collapse)AuthorAgeFilesLines
* Remove deprecated `ConnectionError`Remove-deprecated-ConnectionErrorJeff Widman2019-05-241-4/+0
| | | | | | | This has been deprecated for a bit in favor of `KafkaConnectionError` because it conflicts with Python's built-in `ConnectionError`. Time to remove it as part of cleaning up our old deprecated code.
* Make NotEnoughReplicasError/NotEnoughReplicasAfterAppendError retriable (#1722)le-linh2019-03-031-0/+2
|
* Stop using broker-errors for client-side problemsJeff Widman2018-11-181-0/+4
| | | | | | | | | | | | | `UnsupportedVersionError` is intended to indicate a server-side error: https://github.com/dpkp/kafka-python/blob/ba7372e44ffa1ee49fb4d5efbd67534393e944db/kafka/errors.py#L375-L378 So we should not be raising it for client-side errors. I realize that semantically this seems like the appropriate error to raise. However, this is confusing when debugging... for a real-life example, see https://github.com/Parsely/pykafka/issues/697. So I strongly feel that server-side errors should be kept separate from client-side errors, even if all the client is doing is proactively protecting against hitting a situation where the broker would return this error.
* Remove ConsumerTimeoutJonathan Emord2018-09-271-4/+0
|
* Retain but deprecate kafka.errors.ConnectionError for compatibilityDana Powers2018-05-261-0/+4
|
* Ignore MetadataResponses with empty broker list (#1506)Dana Powers2018-05-261-0/+4
|
* Stop shadowing `ConnectionError`Jeff Widman2018-05-231-3/+3
| | | | | | | | | | In Python3, `ConnectionError` is a native exception. So rename our custom one to `KafkaConnectionError` to prevent accidentally shadowing the native one. Note that there are still valid uses of `ConnectionError` in this code. They already expect a native Python3 `ConnectionError`, and also already handle the Python2 compatibility issues.
* KAFKA-3888 Use background thread to process consumer heartbeats (#1266)Dana Powers2017-12-211-1/+12
|
* Refactor MessageSet and Message into LegacyRecordBatch to later support v2 ↵Taras2017-10-111-2/+5
| | | | message format
* Add kafka.protocol.parser.KafkaProtocol w/ receive and send (#1230)Dana Powers2017-10-101-1/+5
|
* Make UnknownTopicOrPartitionError retriable errorissue1155Taras Voinarovskiy2017-07-301-0/+1
|
* Add new broker response errorsDana Powers2017-03-041-0/+65
|
* Small style fixes in kafka.errorsDana Powers2017-03-041-4/+5
|
* Args are optional in BrokerResponseError str (#889)Dana Powers2016-11-181-3/+3
|
* implement sasl PLAIN mechanismLars Jørgen Solberg2016-08-031-0/+20
|
* Always absolute_importabsolute_importDana Powers2016-08-021-0/+2
|
* Explicit format string argument indices for python 2.6 compatibilityDana Powers2016-07-171-2/+2
|
* Cleanup error logging (#760 / #759)Dana Powers2016-07-151-1/+11
| | | | | | - add error type to all KafkaErrors - add args to BrokerResponseError - drop description from BrokerResponseError - fix bug logging errbacks as callbacks
* tweak spelling mistake (#719)steve89182016-06-171-1/+1
|
* Use standard LZ4 framing for v1 messages / kafka 0.10 (#695)Dana Powers2016-05-221-2/+2
| | | | | | * LZ4 framing fixed in 0.10 / message v1 -- retain broken lz4 code for compatibility * lz4f does not support easy incremental decompression - raise RuntimeError * Update lz4 codec tests
* Use Fetch/Produce API v2 for brokers >= 0.10 (uses message format v1) (#694)Dana Powers2016-05-221-0/+6
|
* Kafka metrics java port. No reporters or instrumentation.Zack Dever2016-04-131-0/+4
| | | | | There is no straight translation for the JMX reporter into python, so I'll do something else in a separate commit.
* KAFKA-3318: clean up consumer logging and error messagesDana Powers2016-04-051-0/+4
|
* Split kafka.common into kafka.structs and kafka.errorsDana Powers2016-04-051-0/+399
View Lorry Controller Status