Releases: karafka/waterdrop
Releases · karafka/waterdrop
v2.4.11
- Replace the local rspec locator with generalized core one.
- Make
::WaterDrop::Instrumentation::Notifications::EVENTS
list public for anyone wanting to re-bind those into a different notification bus.
v2.4.10
- Include
caller
in the error instrumentation to align with Karafka.
v2.4.9
- Remove empty debug logging out of
LoggerListener
.
- Do not lock Ruby version in Karafka in favour of
karafka-core
.
- Make sure
karafka-core
version is at least 2.0.9
to make sure we run karafka-rdkafka
.
v2.4.8
- Use monotonic time from Karafka core.
v2.4.7
- Add support to customizable middlewares that can modify message hash prior to validation and dispatch.
- Fix a case where upon not-available leader, metadata request would not be retried
- Require
karafka-core
2.0.7.
v2.4.6
- Set
statistics.interval.ms
to 5 seconds by default, so the defaults cover all the instrumentation out of the box.
Upgrade notes
If you want to disable librdkafka
statistics because you do not use them at all, update the kafka
statistics.interval.ms
setting and set it to 0
:
producer = WaterDrop::Producer.new
producer.setup do |config|
config.deliver = true
config.kafka = {
'bootstrap.servers': 'localhost:9092',
'statistics.interval.ms': 0
}
end
v2.4.5
- Fix invalid error scope visibility.
- Cache partition count to improve messages production and lower stress on Kafka when
partition_key
is on.
v2.4.4
- Add a temporary patch on top of
rdkafka-ruby
to mitigate metadata fetch timeout failures.
v2.4.3
- Support for librdkafka 0.13
- Update Github Actions
- Change auto-generated id from
SecureRandom#uuid
to SecureRandom#hex(6)
- Remove shared components that were moved to
karafka-core
from WaterDrop
v2.4.2
- Allow sending tombstone messages (#267)