> jdk. attach is needed for nodetool sjk hh. When someone tries to use
> that command, they get an error that JDK is expected. There isn't
> anything to do about that here.
Given we have functionality that depends on a JDK, and all our testing is done
with a JDK, I'm in favour of printing a warning that JDK is recommended, from
5.0 onwards. And before 5.0 just leaving things in the state they are in.
This is a problem with the dockerhub images, and our debian and redhat packages.
I suggest, for expediency, to
- put a nice failure message in Sjk.java (e.g. "JDK required for this nodetool
command"),
- add a comment in cassandra.yaml in front of audit_logging_options stating
compatibility with JRE is unknown (referencing the jira issue), and
- add the jdk add-opens and add-exports only when jdk is detected (javac is on
path).
And, is debugging info is of concern here ? i.e. if debug info is only in the
JDK's jvm and it is valuable to us (over any perf diff), then we have reason to
recommend the jdk.
