[
https://issues.apache.org/jira/browse/CASSANDRA-8765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylvain Lebresne resolved CASSANDRA-8765.
-----------------------------------------
Resolution: Won't Fix
I haven't heard of much complaints about the Snappy dependency being a huge
problem, especially since I believe we don't default on Snappy for anything by
default anymore. And I don't think anyone has the time to do the proper
benchmarking homework that should ideally be done for this, so closing.
Of course if someone with spare time cares about this enough to do proper
benchmarking and present the result here, happy to re-evaluate.
> Switch to a pure Java implementation of Snappy to reduce compatibility issues
> -----------------------------------------------------------------------------
>
> Key: CASSANDRA-8765
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8765
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Michaël Figuière
> Priority: Minor
>
> Since it has been introduced as a dependency, the Xerial's Snappy library,
> which relies on a few native libraries for performance purpose, has caused
> several compatibility issue or unexpected behaviors.
> Dain's implementation (https://github.com/dain/snappy) is written in pure
> Java using some {{Unsafe}} memory access for secure its performance.
> According to the benchmark published by its author
> (https://github.com/dain/snappy#block-compress), it ends up being often
> faster than the JNI implementation, but without the compatibility issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
