[
https://issues.apache.org/jira/browse/CASSANDRA-18688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17755652#comment-17755652
]
shylaja kokoori commented on CASSANDRA-18688:
---------------------------------------------
Mick, to answer your questions
{quote}How difficult is it to edit the bin/cassandra script (or
cassandra.in.sh) for them to get what they want ?
{quote}
Like, Ekaterina said, currently we are allowing versions 11, 17 and anything
above. With current patch, server bring up fails if not a supported version.
bin/cassandra.in.sh changes are not difficult, but there is a bit of learning
curve in my opinion, if one is new to the code.
{quote}What signal (advertently or not) are we giving by providing the `-J`
option ? Would a env var be a better signal ? (I think the use of `-J`, if we
accept it, should still print a loud warning.)
{quote}
-J option is inline with -R, f etc. we already provide for bin/cassandra. By
env var, I assume you mean something like what we had to enable JDK11 in 4.x,
with a -D. This maybe a better option perhaps, if we want to do something
similar with scripts in tools folder. Regardless, I feel providing an option
from command line will be convenient. I agree, with everyone the message needs
to be louder than what I have.
> Limit Java runtime in 5.0 to JDK 11 and 17 in scripts; add a flag to opt out
> of that
> ------------------------------------------------------------------------------------
>
> Key: CASSANDRA-18688
> URL: https://issues.apache.org/jira/browse/CASSANDRA-18688
> Project: Cassandra
> Issue Type: Task
> Components: Build
> Reporter: Ekaterina Dimitrova
> Assignee: shylaja kokoori
> Priority: Normal
> Fix For: 5.0.x
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Currently, we limit our users from building with non-default Java versions in
> build.xml.
> They can easily hack build.xml for test purposes with different versions.
> Cassandra–5.0 will be run on JDK11 and JDK17, but on startup, we do not limit
> people to those two, but only to everything >= 11. We should also put an
> upper limit of 17 in our Cassandra startup scripts. We can also add a flag to
> opt-out if someone wants to test with newer versions.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
