Skip to content

lz4j: use safeDecompressor instead of fastDecompressor#18930

Merged
cryptoe merged 1 commit intoapache:masterfrom
kgyrtkirk:lz4-safe
Jan 20, 2026
Merged

lz4j: use safeDecompressor instead of fastDecompressor#18930
cryptoe merged 1 commit intoapache:masterfrom
kgyrtkirk:lz4-safe

Conversation

@kgyrtkirk
Copy link
Member

  • the fastDecompressor method is deprecated
  • according to lz4 apidoc-s the fast could be even slower

https://github.com/yawkat/lz4-java/blob/384ade4e11ca33002e600449682e5ebb63b85ac8/src/java/net/jpountz/lz4/LZ4Factory.java#L82-L89

@kgyrtkirk kgyrtkirk added this to the 36.0.0 milestone Jan 19, 2026
Copy link
Contributor

@cryptoe cryptoe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just wanted to check if there are any backward compatibility concerns during rolling upgrade etc that we need to be aware about, or reading older data.

@kgyrtkirk
Copy link
Member Author

It seems to me that lz4 is only used in memcached related classes. But he decoders should work the same - there shouldn't be any compatibility issues.

@cryptoe cryptoe merged commit f7f0f9f into apache:master Jan 20, 2026
68 of 69 checks passed
kgyrtkirk added a commit that referenced this pull request Jan 20, 2026
(cherry picked from commit f7f0f9f)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants