Cassandra Stress not working on Java 15+

[CodeLieutenant]

Java 15 removed Nashorn engine, and due to this, cassandra-stress is not working on modern Java versions

[mykaul]

It is continued separately - see https://mvnrepository.com/artifact/org.openjdk.nashorn/nashorn-core

[fruch]

@CodeLieutenant

what's c-s is doing with this engine ? I don't remember any feature we are using and passing into it javascript...

[CodeLieutenant]

@fruch, since this is a Apache Cassandra Codebase (I've remove much of it's source code), there is a possibility in it to define UDFs in Javascript. Thats executed with Nashorn engine, and since c-s is derived from Cassandra's source code, it also does depend on JS engine. There is no scripting available to c-s, but it's really hard to remove it from the source code.

[fruch]

@fruch, since this is a Apache Cassandra Codebase (I've remove much of it's source code), there is a possibility in it to define UDFs in Javascript. Thats executed with Nashorn engine, and since c-s is derived from Cassandra's source code, it also does depend on JS engine. There is no scripting available to c-s, but it's really hard to remove it from the source code.

Why it's hard, if we don't have any functionality in c-s using it directly ?

[fruch]

I rather invest in taking it out of the code, then invest in replacing the library

[CodeLieutenant]

I was thinking the same, removing it would be great if it's possible, replacing the library can be a temporary fix if needed.
But good solution is to remove it completly

[CodeLieutenant]

Why it's hard, if we don't have any functionality in c-s using it directly ?

Cause c-s is using Apache Cassandra as a base, so other classes are referencing the Nashorn and so on, Dep Tree, this make is really hard to remove it

[fruch]

Why it's hard, if we don't have any functionality in c-s using it directly ?

Cause c-s is using Apache Cassandra as a base, so other classes are referencing the Nashorn and so on, Dep Tree, this make is really hard to remove it

It's mentioned only in two files, I think it should be that hard.

Anyhow there is no rush for supporting newer java versions

[fruch]

@CodeLieutenant just for the reference, you were trying using new java version, cause of the work on packaging ? (no one asked for it, if i under correctly)

[CodeLieutenant]

It was accidental discovery, I had Java 21 installed on my machine and forgot to change JAVA_HOME to Java 11 to work with c-s. So none asked for it, but still i wanted to have it logged so that we know c-s does not work with >15 Java

[CodeLieutenant]

After finishing #37 PR, Debian 12 is not packaging Java 11 in their repositories, Ubuntu 24.04 does, but Debian 12 is not, So this means (unless Java 11 is manually installed), we don't support Debian 12 when building .deb packages