I agree that all patches should be added to changes.txt, just to rule out
any ambiguities. When people look at Changes.txt it's usually to find
something specific, not to browse the list of changes. Anything significant
should make it into news.txt, which is more appropriate for users.
changes.txt
Hi,
Cassandra ships with jna in its lib folder, I believe this is the only
dependency necessary. I found it the day I got the same problem you got,
meaning OS Jna overriding Cassandra embedded one
On 18 July 2017 at 15:52, Micha wrote:
>
> ok, if I deinstall the package libjna-jni, which also r
I also think all issues should be kept in CHANGES.txt, it very useful either to
find what changed or to track some obscure bugs months after the release.
Sometime when developing plugins for Cassandra you find solutions/resolution
there.
Maybe if you want to reduce the list you could provide a
On Tue, Jul 18, 2017 at 8:10 AM, Stefan Podkowinski wrote:
> Has there been any consensus in the past about what goes into
> CHANGES.txt and what not? My naive assumption was that the intended
> audience for the file are users who want to know about changes between
> new releases. Having that in m
ok, if I deinstall the package libjna-jni, which also removes
libjna-java, the error is gone and sstabledump works.
On startup cassandras system log still contains "JNA mlockall
successful" which means that jna is working for cassandra.
I thought this lib is necessary for using JNA?
Michael
Has there been any consensus in the past about what goes into
CHANGES.txt and what not? My naive assumption was that the intended
audience for the file are users who want to know about changes between
new releases. Having that in mind, I skipped changes.txt once in a while
for updates that have no
Debian jessie, cassandra 3.11 binary debian install (which comes from
dl.bintray.com/apache/cassandra/ )
apt-cache policy shows that the version of the jna lib is 4.1.0
java 8 is a backport for jessie.
(not 4.0.0 , which is shown by sstabledump)
Cassandra itself doesn't show any error about jna
I haven't been able to reproduce this on Ubuntu or CentOS. Which OS do
you use? Did you install a pre-build package or tarball?
On 18.07.2017 11:43, Micha wrote:
> Hello,
>
> when calling sstabledump from cassandra 3.11 I get the error:
>
>
> "There is an incompatible JNA native library install
Hello,
when calling sstabledump from cassandra 3.11 I get the error:
"There is an incompatible JNA native library installed on this system
Expected: 5.1.0
Found: 4.0.0"
Maybe I overlooked something, but after searching I found the newest
version to be 4.4 with 4.5 the upcoming new version.
My
