-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zstd version is incompatible with the version of Zstd used by the Kafka Indexing service #11816
Comments
Hi! I know what happened! I used to test ZSTD on Kafka. It was caused by commit 10123. You can see ZstdFactory.java, there is |
@rpless Have you verified the newer Zstd version works with parquet and avro extensions? I think we also need to add some IT test cases that produce Zstd compressed data to cover this edge case. |
If compile can pass, I think the risk is low. Because it means API is not changed. |
@FrankChen021 I have not had a chance to test those extensions. I did look quickly and I think I may have been wrong about avro depending on it, so it may only be the parquet extension that needs a test. |
Hi, I got same error. Here is sample error log.
|
This is not an issue in 0.20.1. We upgraded from 0.20.1 to 0.22.1 and started getting this issue. |
Current workaround: For each node in the cluster, replace |
it was fixed by #12408 |
Affected Version
This issue affects 0.22.0 but also probably affects 0.21.x and 0.20.x.
Description
Currently Druid relies on version 1.3.3-1 of zstd. However, the Kafka client used in the Kafka Indexing Service relies on version 1.5.0-4.
When you attempt to ingest data from Kafka that has been compressed with zstd it yields the following exception and fails the indexing task:
I have manually linked the 1.5.0-4 zstd jar into a Druid cluster and this fixes the issue with the Kafka indexing service, however I also had to replace this jar in both the parquet and avro extensions and I have not yet verified that they still work.
The text was updated successfully, but these errors were encountered: