| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
messagesets
|
|
|
| |
Fixes #665
|
| |
|
| |
|
| |
|
|\
| |
| | |
Small improvements to fetching logic
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
FetchResponses
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Generally should not init_fetches while the generator has pending
messages; this revision adds an explicit check / noop to the
public interface, and uses a private method internally to
attempt to pipeline fetch requests.
|
| |
|
| |
|
| |
|
|
|
|
| |
out of sync
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- Support single message consumption via next(consumer) in py2/py3
- batch message methods (Fetcher.fetched_records / KafkaConsumer.poll)
are incompatible with iterators -- message generator state keeps
messages internally after they are popped from _records, but before
subscription_state is updated.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
- manages fetch requests via async client and subscription_state
- based on upstream java client
|