[
https://issues.apache.org/jira/browse/CASSANDRA-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975512#action_12975512
]
Eric Evans edited comment on CASSANDRA-1908 at 12/28/10 10:21 AM:
------------------------------------------------------------------
It might be trivial to implement a JNI library, but I don't think it's going to
be trivial to build architecture dependent code at release time, field issues,
debug, etc, for N platforms.
I'm also open to alternatives, but I'd need to be convinced that the cure
wasn't worse than the disease.
was (Author: urandom):
It might be trivial to implement a JNI library, but I don't think it's
going to be trivial to build architecture dependent code at release time,
field issues, debug, etc, for N platforms.
I'm also open to alternatives, but I'd need to be convinced that the cure
wasn't worth the disease.
> 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.
