diff options
| author |   Rashmi Pujar <rashmi.pujar1@bell.ca> | 2022-07-27 11:44:04 -0400 |
|---|---|---|
| committer | Rashmi Pujar <rashmi.pujar1@bell.ca> | 2022-07-28 15:23:00 -0400 |
| commit | c6c3fed415006c2ea5c5af21fe9a53936fc8800b (patch) | |
| tree | 007d7ce96b550e2c35ef7ffe2f945c70273f2a07 /tools | |
| parent | c6e16002ed2185b5ed975673df1c40f512b74541 (diff) | |
Bump the version of kafka-clients dependency to 3.0.0
The issue was observed when APEX fails to consume events from
a Kafka topic when message compression is used specifically snappy.
APEX KafkaConsumer uses snappy-java library (transitive
dependency from kafka-clients) to consume events with snappy
compression. The snappy-java jar packages the native
library (built against glibc) which can be overwritten
to use alpine compatible native library (built using musl).
This means we will need to install the java-snappy-package in apex-pdp
which is also added to the commit as an option.
Alternatively, in later version of snappy-java dependency (1.1.8)
there is an option to use Java implementation instead of native
library as per:
https://github.com/xerial/snappy-java#using-pure-java-snappy-implementation.
This is a cleaner solution to fix the issue.
Issue-ID: POLICY-4310
Signed-off-by: Rashmi Pujar <rashmi.pujar1@bell.ca>
Change-Id: Ic92b1d429ca3ca0cd1cd7070cd8d102df58b1420
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions