16 releases (2 stable)
✓ Uses Rust 2018 edition
|new 1.2.2||Dec 4, 2019|
|1.0.0||Apr 26, 2019|
|0.11.6-1||Feb 25, 2019|
|0.11.6-0||Dec 15, 2018|
|0.9.2-0||Nov 26, 2016|
#3 in #kafka
8,045 downloads per month
Used in 10 crates (1 directly)
Low level bindings to librdkafka.
To regenerate the bindings:
git submodule update --init cargo install bindgen ./update-bindings.sh
The rdkafka-sys version number is in the format
corresponds to the librdkafka version, and
P indicates the version of the
When any of librdkafka's optional dependencies are enabled, like libz or OpenSSL, if you have multiple versions of that library installed upon your system, librdkafka's build system may disagree with Cargo about which version of the library to use! This can result in subtly broken builds, if librdkafka compiles against the headers for one version but Cargo links against a different version. For complete confidence when building release binaries, use an environment like a Docker container or a chroot jail where you can guarantee that only one version of each dependency is present. Unfortunately, the current design of Cargo makes this nearly impossible to fix.
librdkafka's default build system, which uses a bespoke tool called mklove, is somewhat unreliable, as it does not support out-of-tree builds. This means that if you have multiple projects that depend on the same version of
librdkafka, they will share a build directory in
~/.cargo/registry, and builds from one project may corrupt builds from the other. Using the CMake based build system is strongly encouraged, if you can take the dependency on CMake.
By default a submodule with the librdkafka sources pinned to a specific commit will be used to compile and statically link the library.
dynamic-linking feature can be used to link rdkafka to a locally
installed version of librdkafka: if the feature is enabled, the build script
pkg-config to check the version of the library installed in the
system, and it will configure the compiler to dynamically link against it.
The following features directly correspond to librdkafka features (i.e., flags
you would pass to
configure if you were compiling manually).
sslfeature enables SSL support. By default, the system's OpenSSL library is dynamically linked, but static linking of the version bundled with the openssl-sys crate can be requested with the
gssapifeature enables SASL GSSAPI support with Cyrus libsasl2. This feature requires that libsasl2 is installed on the system, as there is not yet a libsasl2-sys crate that can build and link against a bundled copy of the library.
libzfeature enables support for zlib compression. This feature is enabled by default. By default, the system's libz is dynamically linked, but static linking of the version bundled with the libz-sys crate can be requested with the
zstdfeature enables support for ZSTD compression. By default, this builds and statically links the version bundled with the zstd-sys crate, but dynamic linking of the system's version can be requested with the
external-lz4feature statically links against the copy of liblz4 bundled with the lz4-sys crate. By default, librdkafka statically links against its own bundled version of liblz4. Due to limitations with lz4-sys, it is not yet possible to dynamically link against the system's version of liblz4.
All features are disabled by default unless noted otherwise above. The build
process is defined in
To upgrade change the git submodule in
librdkafka, check if new errors
need to be added to
helpers::primive_to_rd_kafka_resp_err_t and update
the version in