Changelog History
Page 1
-
v0.1.16 Changes
March 27, 2018- โ Tested 0.1.16-alpha01
-
v0.1.16-alpha01 Changes
- ๐ BUG: memory leak in 0.1.15.
-
v0.1.15 Changes
๐ฅ BREAKING:
FetchResponse
item now explicit structure rather than tuple. Breaking only if using low-level Fetch API.BUG: consumer doesn't recover from
leaderless_partition_detected
#204BUG: consumer would enter an infinite loop between
offsets_out_of_range
andresuming_fetch_from_reset_offsets
๐ BUG: stalled consumers after TCP connection timeout
๐ BUG: offsets committed for partitions which are no longer assigned after a rebalance
๐ FEATURE:
ConsumerConfig.fetchMaxBytesOverride
allows increasingfetchMaxBytes
to a ceiling on message too big exceptions.๐ FEATURE:
ProducerQueueType
to allow configuration of producer message queue networks.๐ IMPROVE: support for v0.11 of broker protocol, including v5 of Fetch and v3 of Produce APIs
IMPROVE: logging where
received_empty_buffer
logged asINFO
message as it doesn't indicate an error๐ IMPROVE: connection managemeng to ensure only a single TCP connection per broker per Kafka connection
๐ IMPROVE: Reduce recovery time from broker restarts and rebalancing
๐ IMPROVE: improved TCP connection logging and log levels to reduce "false positives"
๐ IMPROVE: .NET Standard support
-
v0.1.15-alpha05 Changes
- ๐ BUG: ensure CRC check runs with respect to appropriate message version (magic byte)
-
v0.1.15-alpha04 Changes
March 19, 2018- ๐ BUG: compression works when using v0.11 (auto) protocol
-
v0.1.15-alpha02 Changes
- ๐ IMPROVE: support for v0.11 of broker protocol, including v5 of Fetch and v3 of Produce APIs
- ๐ IMPROVE: improved TCP connection logging and log levels to reduce "false positives"
- ๐ฅ BREAKING: FetchResponse item now explicit structure rather than tuple. Breaking only if using low-level Fetch API.
- ๐ FEATURE:
ProducerQueueType
to allow configuration of producer message queue networks. - BUG: consumer doesn't recover from
leaderless_partition_detected
#204
-
v0.1.15-alpha01 Changes
March 05, 2018- BUG: consumer would enter an infinite loop between
offsets_out_of_range
andresuming_fetch_from_reset_offsets
- ๐ BUG: stalled consumers after TCP connection timeout
- ๐ BUG: offsets committed for partitions which are no longer assigned after a rebalance
- ๐ FEATURE: ConsumerConfig.fetchMaxBytesOverride allows increasing fetchMaxBytes to a ceiling on message too big exceptions.
- IMPROVE: logging where received_empty_buffer logged as INFO message as it doesn't indicate an error
- ๐ IMPROVE: connection managemeng to ensure only a single TCP connection per broker per Kafka connection
- ๐ IMPROVE: Reduce recovery time from broker restarts and rebalancing
- BUG: consumer would enter an infinite loop between
-
v0.1.14-alpha02 Changes
- Adjusting FSharp.Core reference
-
v0.1.14-alpha01 Changes
- .NET Standard + .NET 45 targets
-
v0.1.13 Changes
- ๐ Roll-up of 0.1.13-alpha builds after testing