[
https://issues.apache.org/jira/browse/CASSANDRA-16615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Semb Wever updated CASSANDRA-16615:
-------------------------------------------
Reviewers: (was: Michael Semb Wever)
> Incompatible JNA libraries cause unnecessary failures when using
> cassandra-all jar.
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-16615
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16615
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Other
> Reporter: Doug Rohrer
> Priority: Normal
>
> There are some additional use-cases where lack of JNA libraries is causing
> issues for users of cassandra-all libraries - cases where the native
> libraries were not loaded but we should be able to continue should be handled
> without throwing exceptions. Note that the Cassandra +server+ will not start
> up without an appropriate/compatible JNA jar available, but users of the
> cassandra-all libraries will have a more difficult time maintaining
> compatibility across JNA versions as they deploy to, for example, Spark
> setups that have newer/older JNA versions.
> Proposal:
> - Audit usages of `NativeLibrary`
> - Wherever possible, handle the -1 return values without failing +if
> `DatabaseDescriptor.isClientInitialized()` returns true+.
> - Maintain existing failure behavior if the system is not in client mode but
> the call returns -1.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
