[
https://issues.apache.org/jira/browse/CASSANDRA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975641#action_12975641
]
Peter Schuller commented on CASSANDRA-1908:
-------------------------------------------
I was thinking along those lines (separate project) before when there was some
JNA vs. JNI debate w.r.t. direct I/O. A separate project could that provides
some fairly simple and specific things that tend to be useful in a pragmatic
way, without trying to be overly formal or a complete posix wrapper. It could
be useful for others except Cassandra, and it would remove any build hassle
trade-offs in the JNA vs. JNI decision from Cassandra.
Also, for future work that might imply very frequent mincore() calls, the
calling overhead, if the numbers claimed are correct, could possibly be
significant for Cassandra (although I'm pretty paranoid about the cost of
mincore() to begin with, which might dwarf the JNI vs. JNA issue).
> 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.
