apache / apache/ignite

lz4 upgrade

Open
#11,378 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Java
Stars
5.1k
Forks
1.9k
Avg merge
3d 2h
Merged PRs (30d)
46

Description

Hi Ignite Team,

[org.lz4](https://mvnrepository.com/artifact/net.jpountz.lz4/lz4) has been moved to [lz4-java](https://mvnrepository.com/artifact/org.lz4/lz4-java).
If I use ignite-compress (2.16.0) where org.lz4 has been removed, but the class CompressionProcessorImpl (2.16.0)
in the ignite is still using org.lz4 to compress, which leads to

_Caused by: java.lang.NoClassDefFoundError: net/jpountz/lz4/LZ4Factory
igniteserver-1 | at org.apache.ignite.internal.processors.compress.CompressionProcessorImpl$Lz4.(CompressionProcessorImpl.java:429)
igniteserver-1 | at org.apache.ignite.internal.processors.compress.CompressionProcessorImpl.maxCompressedBufferSize(CompressionProcessorImpl.java:419)
igniteserver-1 | at org.apache.ignite.internal.processors.compress.CompressionProcessorImpl.(CompressionProcessorImpl.java:56)_

do you have any plan to upgrade it to lz4-java as well?

Contributor guide

Open the contributing guide

Research direction

Start with CompressionProcessorImpl, especially the Lz4 initializer around lines 419 and 429, and inspect the ignite-compress dependency declaration. Reproduce the failure with Ignite 2.16.0 and verify that LZ4 compression starts without the NoClassDefFoundError after the dependency references are aligned.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
databases, distributed-systems
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.