Thanks, Mick
It seems that no one had objections to your suggestion so I will move
forward with that:
“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 stati
> 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.
>
Correction: ignore these two sentences. They should ha
> 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 w
Hi everyone,
Some of you remember that Paulo raised a concern around warnings about
missing modules on startup during the 5.0 alpha2 voting.[1]
We opened the ticket CASSANDRA-19001. The problem turned out to be not a
5.0 one.
Those modules are missing when we run Cassandra on JRE. Those warnings
h
