- 💥 Upgrade openssl to v0.10. This may be a breaking change for your application code, since openssl v0.10 is a breaking change. Thanks to @l4l!
- 🔧 Run integration tests on various configurations with compression and encryption.
💥 [BREAKING] Fixed #101. The
Consumerwas erroneously committing the offset of the last consumed message instead of the next offset that it should read, which is what the Kafka protocol specifies it should be. This means that:
- When you upgrade, your consumers will read the last message it consumed again.
- The consumers will now be committing one offset past where they were before. If you've come to rely on this behavior in any way, you should correct it.
v0.6.2August 01, 2017
- 🚀 A purely administrative release - no functional changes compared to v0.6.0
- 📚 Move all documentation to docs.rs
- ⚡️ Update to latest rust-openssl (#122; many thanks to @flier)
- Replace native snappy dependency with rust-snappy (#116; again many thanks to @flier)
- 🐎 Performance improvements by avoiding needless cloning during fetching offsets and API improvements around fetching group offsets (#128; many many thanks to @dead10ck)
- Replace SipHasher with XxHash (#145)
- ➕ Added
Consumer#subscriptionsto inspect the consumed topic-partitions (#137)
- ✅ Started maintaining integration tests (#143; kudos to @dead10ck)
- 👍 Allow borrowing KafkaClient from Consumer/Producer (#136; contributed by @thijsc)
- 0️⃣ Don't send client-id by default; but allow specifying one (#140; contributed by @Morsicus)
- 👍 Kafka group offset storage support (#95)
- 👍 Allow consumer to read topics/partitions without a group (breaking api change) (#105)
- 👌 Support for reading multiple topics through consumer (breaking api change) (#31)
- Type safe required-acks api for sending messages (breaking api change) (#97)
- ✅ Consumer#fallback_offset defaults to "latest" now (#106)
- ⚡️ Update dependency on crc 1.3 (#98)
- Properly evaluate compression type for fetched messages (#96)
⚡️ Update byteorder to 0.5