doc: include reference to lz4 in akka.serialization.jackson.compression #32757
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
patriknw
approved these changes
Jun 30, 2025
There was a problem hiding this comment.
LGTM, I think we can leave the defaults as is. It's documented
For the jackson-cbor and custom bindings other than jackson-json compression is by default disabled, but can be enabled in the same way as the configuration shown above but replacing jackson-json with the binding name (for example jackson-cbor).
johanandren
approved these changes
Jun 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If looking at the reference config, the availability of lz4 for gzip isn't clear since the only reference is when
jackson-jsonoverridescompression. The paradox docs do mention this so it's not entirely undocumented.Semi-related: Jackson's usage of CBOR entails writing field names as values, so for objects that have fieldNamesWhichAreParticularlyLong (not uncommon in Java), CBOR is also rather verbose (and fairly compressible once you start having collections of objects with such field names), so is it worth enabling compression by default in CBOR?