Skip to content

Releases: stackabletech/tokio-zookeeper

0.3.0

07 May 07:36
0.3.0
cf2df9f
Compare
Choose a tag to compare

Changed

  • [BREAKING] Migrated errors from Failure to SNAFU ([#39]).
  • [BREAKING] Migrated from slog to tracing ([#40]).
  • Updated ZooKeeper versions we test against (now 3.9.2, 3.8.4, 3.7.2, 3.6.4, 3.5.10) ([#39]).

0.2.1

13 Feb 07:57
322c90a
Compare
Choose a tag to compare

Changed

  • Don't try to reconnect during exit (#30).

0.2.0

10 Feb 11:14
bd32d91
Compare
Choose a tag to compare

Highlights

tokio-zookeeper now uses futures 0.3 and Tokio 1, which means that it is
now compatible with Rust's async/await syntax!

Migration from 0.1.x

  1. Upgrade the rest of your app to Tokio 1.x (you can use a compatibility wrapper for code such as tokio-zk that still
    uses Tokio 0.1, see
    Cargo.toml
    and
    WithTokio01Executor).
  2. Upgrade tokio-zookeeper to v0.2.
  3. Migrate async calls that thread the ZooKeeper instance to instead borrow it (for example,
    zk.exists(path).and_then(|(zk, stat)| /* do stuff */); becomes
    let stat = zk.exists(path).await?;).
  4. Remove Tokio 0.1 and the compatibility wrapper if they are no longer required.

Added

  • Support all-or-nothing multi-operations (#15).

Changed

  • [BREAKING] Updated to futures 0.3 and Tokio 1, which are compatible with async/await (#19).