[
https://issues.apache.org/jira/browse/CASSANDRA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975603#action_12975603
]
Hiram Chirino commented on CASSANDRA-1908:
------------------------------------------
The JNA solution has all the same architecture dependent code for N platform
problems, what's worse is that it's using a FFI and your hoping that everything
maps out right.
Additionally, because of the FFI, the JNI interface is going to be orders of
magnitude more efficent. See: https://jna.dev.java.net/#performance
But yeah, if you want to include a few pre-built JNI libraries, for example
linux 32/64 and OS X, it's release process gets more complicated as you now
have to build the jni modules on a couple of platforms. To keep that effort to
minimum I'd recommend you guys independently release the jni module and then
just include it as part of the cassandra distribution. Once it stabilizes, you
probably won't be releasing it very often.
> Implement the CLibrary using JNI module to avoid the LGPL dependency on JNA
> ---------------------------------------------------------------------------
>
> Key: CASSANDRA-1908
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1908
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Hiram Chirino
> Fix For: 0.7.1
>
> Attachments: cassandra-jni.zip
>
>
> Cassandra can't ship JNA out of the box since it's LGPL licensed, so many of
> the performance optimizing features in the CLibrary class are not available
> in a simple install. It should be trivial to implement a real JNI library
> for the CLibrary class.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
