[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17621216#comment-17621216
]
Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 11/15/22 3:56 PM:
---
{quote}bring JAMM's functionality in-tree. There's no reason to keep it in a
separate tree
{quote}
Agreed. But I guess this can be done only for trunk and unfortunately we found
out in CASSANDRA-17884 that we have an issue with JDK 11 to solve too.
Also, there _might be_ a different option JDK17+, will get back to this later.
[~skokoori] is looking into different options now, just talked to her today.
She will come back to us with feedback and suggestions when she advances more
with her research on the topic.
was (Author: e.dimitrova):
{quote}bring JAMM's functionality in-tree. There's no reason to keep it in a
separate tree
{quote}
Agreed. But I guess this can be done only for trunk and unfortunately we found
out in CASSANDRA-17884 that we have an issue with JDK 11 to solve too.
Also, there _might be_ a different option JDK17+, will get back to this later.
[~skokoori] is looking into different options now, just talked to her today.
She will come back to us with feedback and suggestions when she advance more
with her research on the topic.
> Support Java 17
> ---
>
> Key: CASSANDRA-16895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16895
> Project: Cassandra
> Issue Type: Epic
> Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 5.x
>
>
> This ticket is intended to group all issues found to support Java 17 in the
> future.
> Upgrade steps:
> * [Dependencies
> |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
> be updated (not all but at least those that require an update in order to
> work with Java 17)
> * More encapsulated JDK internal APIs. Some of the issues might be solved
> with the dependencies updates
> * Currently trunk compiles if we remove the Nashorn dependency (ant script
> tag, used for the test environment; UDFs) . The oracle recommendation to use
> Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
> we will opt in for graal-sdk licensed under UPL
> * All tests to be cleaned
> * CI environment to be setup
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17609788#comment-17609788 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 9/27/22 2:42 AM: -- Short update: * CircleCI POC link expired. I rebased on trunk and posted branch here - [https://github.com/ekaterinadimitrova2/cassandra/tree/16895-trunk-sept] ; New CI run initiated here: [jdk17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/aeac69a7-7132-483f-90c2-31d3200f2499] and [jdk11|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/2c4c1108-06c0-40ac-a591-57bfee60964d] There were more tests failing due to some merge issues as we had soon some reorganization of the pom files. Fixed some of them in the last commit and rerun some of the affected tests successfully. Overall current trunk didn't change too much from when I tested in late March * In order to be able to compile with jdk17, I just commented out the scripted UDFs related code and also commented out related tests to remove the noise until proper removal happen in CASSANDRA-17281. That one will wait a bit as there were some discussions on refactoring in that area of the code. * I am revising separately current accesses we already have to JDK internals. Opening tickets and updating carefully dependencies in separate tickets. * Regarding the JDK outreach program, I contacted an Oracle representative who confirmed Cassandra will be added. So far I still have issues to access their private discussion list. I will have to ping them again... was (Author: e.dimitrova): Short update: * CircleCI POC link expired. I rebased on trunk and posted it here - [https://github.com/ekaterinadimitrova2/cassandra/tree/16895-trunk-sept] ; New CI run initiated here: [jdk17|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/aeac69a7-7132-483f-90c2-31d3200f2499] and [jdk11|https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1949/workflows/2c4c1108-06c0-40ac-a591-57bfee60964d] There were more tests failing due to some merge issues as we had soon some reorganization of the pom files. Fixed some of them in the last commit and rerun some of the affected tests successfully. Overall current trunk didn't change too much from when I tested in late March * In order to be able to compile with jdk17, I just commented out the scripted UDFs related code and also commented out related tests to remove the noise until proper removal happen in CASSANDRA-17281. That one will wait a bit as there were some discussions on refactoring in that area of the code. * I am revising separately current accesses we already have to JDK internals. Opening tickets and updating carefully dependencies in separate tickets. * Regarding the JDK outreach program, I contacted an Oracle representative who confirmed Cassandra will be added. So far I still have issues to access their private discussion list. I will have to ping them again... > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 5.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509143#comment-17509143
]
Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 3/19/22, 2:38 AM:
---
Short update:
The bytebuddy issue was solved. I realized I have to update mockito which was
dependent on an old version of bytebuddy.
After update this is the latest CI run for Java 17:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]
*CQLSH tests:*
* test_round_trip_random is failing with vnodes due to
{code:java}
Exception encountered during startup: The number of initial tokens (by
initial_token) specified (0) is different from num_tokens value (16){code}
Sounds weird, have to investigate it
*DTests:*
* test_oversized_mutation - known failure on trunk
* test_sjk - I just noticed we need to start Cassandra with _--add-exports
jdk.attach/sun.tools.attach=ALL-UNNAMED_ and then SJK works fine. Also, I
updated the SJK to the latest version
* There are 4 UDF functions I broke, please, ignore for now; just noise at
this point
* test_archiving_fql, test_archiving and test_fql_nodetool_options fail for
the same reason - a warning in the logs
{code:java}
Slf4jExceptionHandler.java:38 - Failed to shrink file as it exists no
longer{code}
I haven't had the chance to look at this one yet.
* test_batch_and_slice - fails with
{code:java}
Batch too large{code}
This also needs to be investigated
* test_failing_manual_rebuild_index - to be investigated
* test_hintedhandoff_window - I think this is a known issue
*JVM tests:*
* InternodeEncryptionOptionsTest - all failing if we run them together, but
locally when I run them separately
negotiatedProtocolMustBeAcceptedProtocolTest and
allInternodeEncryptionEstablishedTest are the only two failing in that class.
On a quick glance I think they were trying to use TLSv1 which as
[~maulin.vasavada] already mentioned is disabled in Java 17. To be checked
* bulkLoaderSuccessfullyStreamsOverSsl - to be checked; I guess could be again
the TLSv1
* testPreparedBatch, testReprepareNewBehaviour, testUseWithMultipleKeyspaces,
testReprepareTwoKeyspacesNewBehaviour, fuzzTest, startupNewIP,
sameIPFailWithoutReplace, sameIPFailWithoutReplace, mixedModeFuzzTest - all of
them hit CASSANDRA-16304; course of action TBD next week
* noWarningsSinglePartition, noWarningsScan - to be investigated
*Unit tests:*
* a few scripted UDF related tests, to be ignored
* EmptyValuesTest - the whole class; to be investigated
* testNoTreesRetainedAfterDifference - this one is really hungry for more and
more --add-opensI already opened a lot... to be checked further
* testTruncationReleasesLogSpace - this also needs more --add-opens
* testReplace - to be investigated
---
*To summarize -*
* 1 CQLSH python DTest
* 7 DTests failing (1 known fix and 3 failing for one and the same reason)
* 14 JVM tests – 3 probably TLSv1?, 9 because of CASSANDRA-16304
* 4 Unit tets - 2 of them probably just require more add-opens.
I have to take care of Jenkins, some adjustments around Java 11 upgrade tests
as up to now we were running them with Java 8
And I am wondering whether we don't want a feature branch for this one. Also, I
will be looking for reviewers at some point. Anyone interested to test how
things are going, just ping me on Slack. I will probably hit the mailing list
early next week. Have a nice weekend to whoever reads this :D
was (Author: e.dimitrova):
Short update:
The bytebuddy issue was solved. I realized I have to update mockito which was
dependent on an old version of bytebuddy.
After update this is the latest CI run for Java 17:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]
*CQLSH tests:*
* test_round_trip_random is failing with vnodes due to
{code:java}
Exception encountered during startup: The number of initial tokens (by
initial_token) specified (0) is different from num_tokens value (16){code}
Sounds weird, have to investigate it
*DTests:*
* test_oversized_mutation - known failure on trunk
* test_sjk - I just noticed we need to start Cassandra with _--add-exports
jdk.attach/sun.tools.attach=ALL-UNNAMED_ and then SJK works fine. Also, I
updated the SJK to the latest version
* There are 4 UDF functions I broke, please, ignore for now; just noise at
this point
* test_archiving_fql, test_archiving and test_fql_nodetool_options fail for
the same reason - a warning in the logs
{code:java}
Slf4jExceptionHandler.java:38 - Failed to shrink file as it exists no
longer{code}
I haven't had the chance to look at this one yet.
* test_batch_and_slice - fails with
{code:java}
Batch too large{code}
This also needs to be investigated
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509143#comment-17509143
]
Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 3/19/22, 2:37 AM:
---
Short update:
The bytebuddy issue was solved. I realized I have to update mockito which was
dependent on an old version of bytebuddy.
After update this is the latest CI run for Java 17:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]
*CQLSH tests:*
* test_round_trip_random is failing with vnodes due to
{code:java}
Exception encountered during startup: The number of initial tokens (by
initial_token) specified (0) is different from num_tokens value (16){code}
Sounds weird, have to investigate it
*DTests:*
* test_oversized_mutation - known failure on trunk
* test_sjk - I just noticed we need to start Cassandra with _--add-exports
jdk.attach/sun.tools.attach=ALL-UNNAMED_ and then SJK works fine. Also, I
updated the SJK to the latest version
* There are 4 UDF functions I broke, please, ignore for now; just noise at
this point
* test_archiving_fql, test_archiving and test_fql_nodetool_options fail for
the same reason - a warning in the logs
{code:java}
Slf4jExceptionHandler.java:38 - Failed to shrink file as it exists no
longer{code}
I haven't had the chance to look at this one yet.
* test_batch_and_slice - fails with
{code:java}
Batch too large{code}
This also needs to be investigated
* test_failing_manual_rebuild_index - to be investigated
* test_hintedhandoff_window - I think this is a known issue
*JVM tests:*
* InternodeEncryptionOptionsTest - all failing if we run them together, but
locally when I run them separately
negotiatedProtocolMustBeAcceptedProtocolTest and
allInternodeEncryptionEstablishedTest are the only two failing in that class.
On a quick glance I think they were trying to use TLSv1 which as
[~maulin.vasavada] already mentioned is disabled in Java 17. To be checked
* bulkLoaderSuccessfullyStreamsOverSsl - to be checked; I guess could be again
the TLSv1
* testPreparedBatch, testReprepareNewBehaviour, testUseWithMultipleKeyspaces,
testReprepareTwoKeyspacesNewBehaviour, fuzzTest, startupNewIP,
sameIPFailWithoutReplace, sameIPFailWithoutReplace, mixedModeFuzzTest - all of
them hit CASSANDRA-16304; course of action TBD next week
* noWarningsSinglePartition, noWarningsScan - to be investigated
*Unit tests:*
* a few scripted UDF related tests, to be ignored
* EmptyValuesTest - the whole class; to be investigated
* testNoTreesRetainedAfterDifference - this one is really hungry for more and
more --add-opensI already opened a lot... to be checked further
* testTruncationReleasesLogSpace - this also needs more --add-opens
* testReplace - to be investigated
---
*To summarize -*
* 1 CQLSH python DTest
* 7 DTests failing (1 known fix and 3 failing for one and the same reason)
* 14 JVM tests – 3 probably TLSv1?, 9 because of CASSANDRA-16304
* 4 Unit tets - 2 of them probably just require more add-opens.
I have to take care of Jenkins, some adjustments around Java 11 upgrade tests
as up to now we were running them with Java 8
And I am wondering whether we don't want a feature branch for this one. Also, I
will be looking for reviewers at some point. Anyone interested to test how
things are going, just ping me on Slack
was (Author: e.dimitrova):
Short update:
The bytebuddy issue was solved. I realized I have to update mockito which was
dependent on an old version of bytebuddy.
After update this is the latest CI run for Java 17:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]
*CQLSH tests:*
* test_round_trip_random is failing with vnodes due to
{code:java}
Exception encountered during startup: The number of initial tokens (by
initial_token) specified (0) is different from num_tokens value (16){code}
Sounds weird, have to investigate it
*DTests:*
* test_oversized_mutation - known failure on trunk
* test_sjk - I just noticed we need to start Cassandra with _--add-exports
jdk.attach/sun.tools.attach=ALL-UNNAMED_ and then SJK works fine. Also, I
updated the SJK to the latest version
* There are 4 UDF functions I broke, please, ignore for now; just noise at
this point
* test_archiving_fql, test_archiving and test_fql_nodetool_options fail for
the same reason - a warning in the logs
{code:java}
Slf4jExceptionHandler.java:38 - Failed to shrink file as it exists no
longer{code}
I haven't had the chance to look at this one yet.
* test_batch_and_slice - fails with
{code:java}
Batch too large{code}
This also needs to be investigated
* test_failing_manual_rebuild_index - to be investigated
* test_hintedhandoff_window - I think this
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17509143#comment-17509143
]
Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 3/19/22, 2:37 AM:
---
Short update:
The bytebuddy issue was solved. I realized I have to update mockito which was
dependent on an old version of bytebuddy.
After update this is the latest CI run for Java 17:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]
*CQLSH tests:*
* test_round_trip_random is failing with vnodes due to
{code:java}
Exception encountered during startup: The number of initial tokens (by
initial_token) specified (0) is different from num_tokens value (16){code}
Sounds weird, have to investigate it
*DTests:*
* test_oversized_mutation - known failure on trunk
* test_sjk - I just noticed we need to start Cassandra with _--add-exports
jdk.attach/sun.tools.attach=ALL-UNNAMED_ and then SJK works fine. Also, I
updated the SJK to the latest version
* There are 4 UDF functions I broke, please, ignore for now; just noise at
this point
* test_archiving_fql, test_archiving and test_fql_nodetool_options fail for
the same reason - a warning in the logs
{code:java}
Slf4jExceptionHandler.java:38 - Failed to shrink file as it exists no
longer{code}
I haven't had the chance to look at this one yet.
* test_batch_and_slice - fails with
{code:java}
Batch too large{code}
This also needs to be investigated
* test_failing_manual_rebuild_index - to be investigated
* test_hintedhandoff_window - I think this is a known issue
*JVM tests:*
* InternodeEncryptionOptionsTest - all failing if we run them together, but
locally when I run them separately
negotiatedProtocolMustBeAcceptedProtocolTest and
allInternodeEncryptionEstablishedTest are the only two failing in that class.
On a quick glance I think they were trying to use TLSv1 which as
[~maulin.vasavada] already mentioned is disabled in Java 17. To be checked
* bulkLoaderSuccessfullyStreamsOverSsl - to be checked; I guess could be again
the TLSv1
* testPreparedBatch, testReprepareNewBehaviour, testUseWithMultipleKeyspaces,
testReprepareTwoKeyspacesNewBehaviour, fuzzTest, startupNewIP,
sameIPFailWithoutReplace, sameIPFailWithoutReplace, mixedModeFuzzTest - all of
them hit CASSANDRA-16304; course of action TBD next week
* noWarningsSinglePartition, noWarningsScan - to be investigated
*Unit tests:*
* a few scripted UDF related tests, to be ignored
* EmptyValuesTest - the whole class; to be investigated
* testNoTreesRetainedAfterDifference - this one is really hungry for more and
more --add-opensI already opened a lot... to be checked further
* testTruncationReleasesLogSpace - this also needs more --add-opens
* testReplace - to be investigated
---
*To summarize -*
* 1 CQLSH python DTest
* 7 DTests failing (1 known fix and 3 failing for one and the same reason)
* 14 JVM tests – 3 probably TLSv1?, 9 because of CASSANDRA-16304
* 4 Unit tets - 2 probably just require more add-opens.
I have to take care of Jenkins, some adjustments around Java 11 upgrade tests
as up to now we were running them with Java 8
And I am wondering whether we don't want a feature branch for this one. Also, I
will be looking for reviewers at some point. Anyone interested to test how
things are going, just ping me on Slack
was (Author: e.dimitrova):
Short update:
The bytebuddy issue was solved. I realized I have to update mockito which was
dependent on an old version of bytebuddy.
After update this is the latest CI run for Java 17:
[https://app.circleci.com/pipelines/github/ekaterinadimitrova2/cassandra/1481/workflows/9f065c12-4c3d-4d6e-b9fc-ee4eb8c5f38b]
*CQLSH tests:*
* test_round_trip_random is failing with vnodes due to
{code:java}
Exception encountered during startup: The number of initial tokens (by
initial_token) specified (0) is different from num_tokens value (16){code}
Sounds weird, have to investigate it
*DTests:*
* test_oversized_mutation - known failure on trunk
* test_sjk - I just noticed we need to start Cassandra with _--add-exports
jdk.attach/sun.tools.attach=ALL-UNNAMED_ and then SJK works fine. Also, I
updated the SJK to the latest version
* There are 4 UDF functions I broke, please, ignore for now; just noise at
this point
* test_archiving_fql, test_archiving and test_fql_nodetool_options fail for
the same reason - a warning in the logs
{code:java}
Slf4jExceptionHandler.java:38 - Failed to shrink file as it exists no
longer{code}
I haven't had the chance to look at this one yet.
* test_batch_and_slice - fails with
{code:java}
Batch too large{code}
This also needs to be investigated
* test_failing_manual_rebuild_index - to be investigated
* test_hintedhandoff_window - I think this is a kn
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508583#comment-17508583
]
Maulin Vasavada edited comment on CASSANDRA-16895 at 3/18/22, 5:12 PM:
---
I guess it could be because prior TLS versions ({-}before{-} prior to TLSv1.2)
are disabled in JDK 17 and the python client in python 3.8 might be defaulting
to those. Not sure though, trying to look into it more.
was (Author: maulin.vasavada):
I guess it could be because prior TLS versions (before TLSv1.2) are disabled in
JDK 17 and the python client in python 3.8 might be defaulting to those. Not
sure though, trying to look into it more.
> Support Java 17
> ---
>
> Key: CASSANDRA-16895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16895
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> This ticket is intended to group all issues found to support Java 17 in the
> future.
> Upgrade steps:
> * [Dependencies
> |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
> be updated (not all but at least those that require an update in order to
> work with Java 17)
> * More encapsulated JDK internal APIs. Some of the issues might be solved
> with the dependencies updates
> * Currently trunk compiles if we remove the Nashorn dependency (ant script
> tag, used for the test environment; UDFs) . The oracle recommendation to use
> Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
> we will opt in for graal-sdk licensed under UPL
> * All tests to be cleaned
> * CI environment to be setup
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508959#comment-17508959
]
Maulin Vasavada edited comment on CASSANDRA-16895 at 3/18/22, 5:11 PM:
---
Yes I am with you guys [~brandon.williams] and [~e.dimitrova] . I meant
versions prior to TLSv1.2 are disabled in Jdk 17. Hence my initial guess was -
what TLS protocol it uses when we trigger the run_cqlsh() from the python test.
If that was passing/using older version of the TLS than v1.2 it could fail.
Basically, if my understanding is right, the test is running cqlsh to describe
namespace and uses ssl options specifying the certificate so I assume it
connects to the node started by the test over ssl.
However based on Ekaterina's findings it seems the Netty upgrade may be the
cause of the underlying failure. My initial research was just based on the test
run logs I could see `assert "Connection e...c:2635)')})\n" == '' - Connection
error: ('Unable to connect to any servers',
{'127.0.0.1:9042': ConnectionShutdown('[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1
alert internal error (_ssl.c:2635)')}
)` .
All-in-all, I believe we don't need to further suspect TLS at this point?
Please let me know otherwise, I can debug further.
was (Author: maulin.vasavada):
Yes I am with you guys [~brandon.williams] and [~e.dimitrova] . I meant
versions prior to TLSv1.2 are disabled in Jdk 17. Hence my initial guess was -
what TLS protocol it uses when we trigger the run_cqlsh() from the python test.
If that was passing/using older version of the TLS than v1.2 it could fail.
Basically, if my understanding is right, the test is running cqlsh to describe
namespace and uses ssl options specifying the certificate so I assume it
connects to the node started by the test via ssl.
However based on Ekaterina's findings it seems the Netty upgrade may be the
cause of the underlying failure. My initial research was just based on the test
run logs I could see `assert "Connection e...c:2635)')})\n" == '' - Connection
error: ('Unable to connect to any servers', {'127.0.0.1:9042':
ConnectionShutdown('[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal
error (_ssl.c:2635)')})` .
All-in-all, I believe we don't need to further suspect TLS at this point?
Please let me know otherwise, I can debug further.
> Support Java 17
> ---
>
> Key: CASSANDRA-16895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16895
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> This ticket is intended to group all issues found to support Java 17 in the
> future.
> Upgrade steps:
> * [Dependencies
> |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
> be updated (not all but at least those that require an update in order to
> work with Java 17)
> * More encapsulated JDK internal APIs. Some of the issues might be solved
> with the dependencies updates
> * Currently trunk compiles if we remove the Nashorn dependency (ant script
> tag, used for the test environment; UDFs) . The oracle recommendation to use
> Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
> we will opt in for graal-sdk licensed under UPL
> * All tests to be cleaned
> * CI environment to be setup
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[
https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508959#comment-17508959
]
Maulin Vasavada edited comment on CASSANDRA-16895 at 3/18/22, 5:11 PM:
---
Yes I am with you guys [~brandon.williams] and [~e.dimitrova] . I meant
versions prior to TLSv1.2 are disabled in Jdk 17. Hence my initial guess was -
what TLS protocol it uses when we trigger the run_cqlsh() from the python test.
If that was passing/using older version of the TLS than v1.2 it could fail.
Basically, if my understanding is right, the test is running cqlsh to describe
namespace and uses ssl options specifying the certificate so I assume it
connects to the node started by the test via ssl.
However based on Ekaterina's findings it seems the Netty upgrade may be the
cause of the underlying failure. My initial research was just based on the test
run logs I could see `assert "Connection e...c:2635)')})\n" == '' - Connection
error: ('Unable to connect to any servers', {'127.0.0.1:9042':
ConnectionShutdown('[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal
error (_ssl.c:2635)')})` .
All-in-all, I believe we don't need to further suspect TLS at this point?
Please let me know otherwise, I can debug further.
was (Author: maulin.vasavada):
Yes I am with you guys [~brandon.williams] and [~e.dimitrova] . I meant
versions prior to TLSv1.2 are disabled in Jdk 17. Hence my initial guess was -
what TLS protocol it uses when we trigger the run_cqlsh() from the python test.
If that was passing/using older version of the TLS than v1.2 it could fail.
However based on Ekaterina's findings it seems the Netty upgrade may be the
cause of the underlying failure. My initial research was just based on the test
run logs I could see `assert "Connection e...c:2635)')})\n" == '' - Connection
error: ('Unable to connect to any servers', \{'127.0.0.1:9042':
ConnectionShutdown('[SSL: TLSV1_ALERT_INTERNAL_ERROR] tlsv1 alert internal
error (_ssl.c:2635)')})` .
All-in-all, I believe we don't need to further suspect TLS at this point?
Please let me know otherwise, I can debug further.
> Support Java 17
> ---
>
> Key: CASSANDRA-16895
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16895
> Project: Cassandra
> Issue Type: Task
> Components: Build
>Reporter: Ekaterina Dimitrova
>Assignee: Ekaterina Dimitrova
>Priority: Normal
> Fix For: 4.x
>
>
> This ticket is intended to group all issues found to support Java 17 in the
> future.
> Upgrade steps:
> * [Dependencies
> |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to
> be updated (not all but at least those that require an update in order to
> work with Java 17)
> * More encapsulated JDK internal APIs. Some of the issues might be solved
> with the dependencies updates
> * Currently trunk compiles if we remove the Nashorn dependency (ant script
> tag, used for the test environment; UDFs) . The oracle recommendation to use
> Nashorn-core won't work for the project as it is under GPL 2.0. Most probably
> we will opt in for graal-sdk licensed under UPL
> * All tests to be cleaned
> * CI environment to be setup
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
-
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508570#comment-17508570 ] Maulin Vasavada edited comment on CASSANDRA-16895 at 3/18/22, 5:36 AM: --- [~e.dimitrova] I will check the TLS related error. Since its from python test, I'll take some more time since I am not much familiar with python TLS. was (Author: maulin.vasavada): [~e.dimitrova] I will check the TLS related error. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508570#comment-17508570 ] Maulin Vasavada edited comment on CASSANDRA-16895 at 3/18/22, 5:33 AM: --- [~e.dimitrova] I will check the TLS related error. was (Author: maulin.vasavada): [~e.dimitrova] Will check the TLS related error. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > Fix For: 4.x > > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17477999#comment-17477999 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 1/18/22, 4:01 PM: --- Quick update - twitter survey: _We would love to understand how you use ApacheCassandra UDFs and UDAs._ _32 people responded as follows:_ * _We do not use them - 75%_ * _We only use Java UDFs - 22%_ * _We only use JS UDFs - 0%_ * _We use Java and JS UDFs - 3%_ We also received feedback on LinkedIN on the topic - [https://www.linkedin.com/feed/update/urn:li:activity:6886728406742970369?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6886728406742970369%2C6886793921020608512%29&replyUrn=urn%3Ali%3Acomment%3A%28activity%3A6886728406742970369%2C6887421509485248512%29] Next I am opening a discussion thread on the dev mailing list to get to some consensus what we do with UDF. I already also found a simple workaround for the ant script and scriptdef so that we don't need Nashorn/Graal/etc for those. (CASSANDRA-17234) was (Author: e.dimitrova): Quick update - twitter survey: _We would love to understand hope you use ApacheCassandra UDFs and UDAs._ _32 people responded as follows:_ * _We do not use them - 75%_ * _We only use Java UDFs - 22%_ * _We only use JS UDFs - 0%_ * _We use Java and JS UDFs - 3%_ We also received feedback on LinkedIN on the topic - https://www.linkedin.com/feed/update/urn:li:activity:6886728406742970369?commentUrn=urn%3Ali%3Acomment%3A%28activity%3A6886728406742970369%2C6886793921020608512%29&replyUrn=urn%3Ali%3Acomment%3A%28activity%3A6886728406742970369%2C6887421509485248512%29 Next I am opening a discussion thread on the dev mailing list to get to some consensus what we do with UDF. I already also found a simple workaround for the ant script and scriptdef so that we don't need Nashorn/Graal/etc for those. (CASSANDRA-17234) > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468309#comment-17468309 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 1/4/22, 1:47 AM: -- I am all in for that, I will open a separate task and discussion thread to reach consensus around the scripted UDFs. Also, I just opened a task to get rid of the ant script tasks (CASSANDRA-17234) and as a consequence not to have to introduce more dependencies; as it was required in order to keep on using the ant script tasks after Java 17 migration. was (Author: e.dimitrova): I am all in for that, I will open a separate task and discussion thread to reach consensus around the scripted UDFs. Also, I just opened a task to get rid of the ant script tasks (CASSANDRA-17234) and as a consequence not to introduce more dependencies as required in order to keep on using the ant script tasks. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449705#comment-17449705 ] Gil Tene edited comment on CASSANDRA-16895 at 11/26/21, 11:19 PM: -- [~benedict] : If popular and free OpenJDK distribution packages were available pre-bundled with JDK+Nashron, would that help keep your packaging simple while allowing people to continue to use Nashron for e.g. UDFs? E.g. Zulu builds of OpenJDK already make pre-bundled JDK+FX packages freely available for similar reasons. was (Author: giltene): [~benedict] : If popular and free OpenJDK distribution packages were available pre-bundled with JDK+Nashron, would that help keep your packaging simple while allowing people to continue to use Nashron for e.g. UDFs? E.g. Zulu builds of OpenJDK already make pre-bundled JDK+FX packages freely for similar reasons. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449705#comment-17449705 ] Gil Tene edited comment on CASSANDRA-16895 at 11/26/21, 11:18 PM: -- [~benedict] : If popular and free OpenJDK distribution packages were available pre-bundled with JDK+Nashron, would that help keep your packaging simple while allowing people to continue to use Nashron for e.g. UDFs? E.g. Zulu builds of OpenJDK already make pre-bundled JDK+FX packages freely for similar reasons. was (Author: giltene): [~benedict] : If popular and free OpenJDK distribution package were available pre-bundled with JDK+Nashron, would that help keep your packaging simple while allowing people to continue to use Nashron for e.g. UDFs? E.g. Zulu builds of OpenJDK already make pre-bundled JDK+FX packages freely for similar reasons. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449652#comment-17449652 ] Gil Tene edited comment on CASSANDRA-16895 at 11/26/21, 6:03 PM: - It’s worth noting that while Nashorn is no longer packaged with the JDK, a standalone Nashorn for Java 11+ is very much available. See the [Nashorn Engine|https://github.com/openjdk/nashorn] and e.g. [coordinates on maven central|https://search.maven.org/artifact/org.openjdk.nashorn/nashorn-core/15.3/jar]. was (Author: giltene): It’s worth noting that while Nashorn is no longer packaged with the JDK, a standalone Nashorn for Java 11+ is very much available. See the [Nashorn Engine|[https://github.com/openjdk/nashorn]] and e.g. [coordinates on maven central|https://search.maven.org/artifact/org.openjdk.nashorn/nashorn-core/15.3/jar]. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449652#comment-17449652 ] Gil Tene edited comment on CASSANDRA-16895 at 11/26/21, 6:02 PM: - It’s worth noting that while Nashorn is no longer packaged with the JDK, a standalone Nashorn for Java 11+ is very much available. See the [Nashorn Engine|[https://github.com/openjdk/nashorn]] and e.g. [coordinates on maven central|https://search.maven.org/artifact/org.openjdk.nashorn/nashorn-core/15.3/jar]. was (Author: giltene): It’s worth noting that while Nashorn is no longer packaged with the JDK, a standalone Nashorn for Java 11+ is very much available. See the [Nashorn Engine|[https://github.com/openjdk/nashorn]] and e.g. [coordinates on maven central|https://search.maven.org/artifact/org.openjdk.nashorn/nashorn-core/15.3/jar]. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17449652#comment-17449652 ] Gil Tene edited comment on CASSANDRA-16895 at 11/26/21, 6:01 PM: - It’s worth noting that while Nashorn is no longer packaged with the JDK, a standalone Nashorn for Java 11+ is very much available. See the [Nashorn Engine|[https://github.com/openjdk/nashorn]] and e.g. [coordinates on maven central|https://search.maven.org/artifact/org.openjdk.nashorn/nashorn-core/15.3/jar]. was (Author: giltene): It’s worth noting that while Nashorn is no longer packaged with the JDK, a standalone Nashorn for Java 11+ is very much available. See the [Nashorn Engine|[https://github.com/openjdk/nashorn],] and e.g. [coordinates on maven central|https://search.maven.org/artifact/org.openjdk.nashorn/nashorn-core/15.3/jar]. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Normal > > This ticket is intended to group all issues found to support Java 17 in the > future. > Upgrade steps: > * [Dependencies > |https://mvnrepository.com/artifact/org.apache.cassandra/cassandra-all/4.0.1]to > be updated (not all but at least those that require an update in order to > work with Java 17) > * More encapsulated JDK internal APIs. Some of the issues might be solved > with the dependencies updates > * Currently trunk compiles if we remove the Nashorn dependency (ant script > tag, used for the test environment; UDFs) . The oracle recommendation to use > Nashorn-core won't work for the project as it is under GPL 2.0. Most probably > we will opt in for graal-sdk licensed under UPL > * All tests to be cleaned > * CI environment to be setup -- This message was sent by Atlassian Jira (v8.20.1#820001) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17413208#comment-17413208 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 9/10/21, 2:20 PM: --- It seems we are good to go as graal-sdk and other required components themselves are under UPL according to Maven and the [GraalVM Readme|https://github.com/oracle/graal#license]. was (Author: e.dimitrova): It seems we are good to go as graal-sdk and other required components are under UPL according to Maven and the [GraalVM Readme|https://github.com/oracle/graal#license]. > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > This ticket is intended to group all issues found to support Java 17 in the > future. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412148#comment-17412148 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 9/8/21, 7:23 PM: -- Some initial thoughts after some initial work done to remove Java 8 and add Java 17 for trunk: - The Nashorn engine has been deprecated in JDK 11 as part of [JEP 335|https://openjdk.java.net/jeps/335] and has been removed from JDK15 as part of [JEP 372|https://openjdk.java.net/jeps/372]. GraalVM can step in as a replacement for JavaScript code previously executed on the Nashorn engine. GraalVM provides all the features for JavaScript previously provided by Nashorn. Working on this part now. - We will need more -add-exports and --add-opens as Java 17 is quite restrictive. - Currently [this script |https://github.com/apache/cassandra/blob/trunk/build.xml#L147-L155]inclusion in build.xml leads to _../cassandra/build.xml:147: Unable to create javax script engine for javascript,_ related to the Nashorn removal. My initial try to solve this didn't work. I left it for later as a lower priority task. - ant updated; probably other dependencies will have to be updated too was (Author: e.dimitrova): Some initial thoughts after some initial work done to remove Java 8 and add Java 17 for trunk: - The Nashorn engine has been deprecated in JDK 11 as part of [JEP 335|https://openjdk.java.net/jeps/335] and and has been removed from JDK15 as part of [JEP 372|https://openjdk.java.net/jeps/372]. GraalVM can step in as a replacement for JavaScript code previously executed on the Nashorn engine. GraalVM provides all the features for JavaScript previously provided by Nashorn. Working on this part now. - We will need more -add-exports and --add-opens as Java 17 is quite restrictive. - Currently [this script |https://github.com/apache/cassandra/blob/trunk/build.xml#L147-L155]inclusion in build.xml leads to _../cassandra/build.xml:147: Unable to create javax script engine for javascript,_ related to the Nashorn removal. My initial try to solve this didn't work. I left it for later as a lower priority task. - ant updated; probably other dependencies will have to be updated too > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > This ticket is intended to group all issues found to support Java 17 in the > future. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412148#comment-17412148 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 9/8/21, 7:23 PM: -- Some initial thoughts after some initial work done to remove Java 8 and add Java 17 for trunk: - The Nashorn engine has been deprecated in JDK 11 as part of [JEP 335|https://openjdk.java.net/jeps/335] and and has been removed from JDK15 as part of [JEP 372|https://openjdk.java.net/jeps/372]. GraalVM can step in as a replacement for JavaScript code previously executed on the Nashorn engine. GraalVM provides all the features for JavaScript previously provided by Nashorn. Working on this part now. - We will need more -add-exports and --add-opens as Java 17 is quite restrictive. - Currently [this script |https://github.com/apache/cassandra/blob/trunk/build.xml#L147-L155]inclusion in build.xml leads to _../cassandra/build.xml:147: Unable to create javax script engine for javascript,_ related to the Nashorn removal. My initial try to solve this didn't work. I left it for later as a lower priority task. - ant updated; probably other dependencies will have to be updated too was (Author: e.dimitrova): Some initial thoughts after some initial work done to remove Java 8 and add Java 17 for trunk: -The Nashorn engine has been deprecated in JDK 11 as part of [JEP 335|https://openjdk.java.net/jeps/335] and and has been removed from JDK15 as part of [JEP 372|https://openjdk.java.net/jeps/372]. GraalVM can step in as a replacement for JavaScript code previously executed on the Nashorn engine. GraalVM provides all the features for JavaScript previously provided by Nashorn. Working on this part now. - We will need more -add-exports and --add-opens as Java 17 is quite restrictive. - Currently [this script |https://github.com/apache/cassandra/blob/trunk/build.xml#L147-L155]inclusion in build.xml leads to _../cassandra/build.xml:147: Unable to create javax script engine for javascript,_ related to the Nashorn removal. My initial try to solve this didn't work. I left it for later as a lower priority task. - ant updated; probably other dependencies will have to be updated too > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > This ticket is intended to group all issues found to support Java 17 in the > future. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Comment Edited] (CASSANDRA-16895) Support Java 17
[ https://issues.apache.org/jira/browse/CASSANDRA-16895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17412148#comment-17412148 ] Ekaterina Dimitrova edited comment on CASSANDRA-16895 at 9/8/21, 7:22 PM: -- Some initial thoughts after some initial work done to remove Java 8 and add Java 17 for trunk: -The Nashorn engine has been deprecated in JDK 11 as part of [JEP 335|https://openjdk.java.net/jeps/335] and and has been removed from JDK15 as part of [JEP 372|https://openjdk.java.net/jeps/372]. GraalVM can step in as a replacement for JavaScript code previously executed on the Nashorn engine. GraalVM provides all the features for JavaScript previously provided by Nashorn. Working on this part now. - We will need more -add-exports and --add-opens as Java 17 is quite restrictive. - Currently [this script |https://github.com/apache/cassandra/blob/trunk/build.xml#L147-L155]inclusion in build.xml leads to _../cassandra/build.xml:147: Unable to create javax script engine for javascript,_ related to the Nashorn removal. My initial try to solve this didn't work. I left it for later as a lower priority task. - ant updated; probably other dependencies will have to be updated too was (Author: e.dimitrova): Some initial thoughts after some initial work done to remove Java 8 and add Java 17 for trunk: -The Nashorn engine has been deprecated in JDK 11 as part of [JEP 335|https://openjdk.java.net/jeps/335] and and has been removed from JDK15 as part of [JEP 372|https://openjdk.java.net/jeps/372]. GraalVM can step in as a replacement for JavaScript code previously executed on the Nashorn engine. GraalVM provides all the features for JavaScript previously provided by Nashorn. Working on this part now. -We will need more --add-exports and --add-opens as Java 17 is quite restrictive. - Currently [this script |https://github.com/apache/cassandra/blob/trunk/build.xml#L147-L155]inclusion in build.xml leads to _../cassandra/build.xml:147: Unable to create javax script engine for javascript,_ related to the Nashorn removal. My initial try to solve this didn't work. I left it for later as a lower priority task. - ant updated; probably other dependencies will have to be updated too > Support Java 17 > --- > > Key: CASSANDRA-16895 > URL: https://issues.apache.org/jira/browse/CASSANDRA-16895 > Project: Cassandra > Issue Type: Task > Components: Build >Reporter: Ekaterina Dimitrova >Assignee: Ekaterina Dimitrova >Priority: Low > > This ticket is intended to group all issues found to support Java 17 in the > future. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
