[
https://issues.apache.org/jira/browse/HADOOP-19574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18019772#comment-18019772
]
ASF GitHub Bot commented on HADOOP-19574:
-----------------------------------------
slfan1989 commented on PR #7892:
URL: https://github.com/apache/hadoop/pull/7892#issuecomment-3283808201
> > @stoty I’d like to confirm with you whether you’d prefer us to create a
separate development branch for you.
> > Pan and I had an offline discussion on this topic. He believes the
changes are manageable and therefore a separate branch may not be necessary. I
think his point makes sense to some extent, but from the perspective of
development efficiency and risk control, I would still recommend creating a
dedicated development branch. This would allow us to iterate more quickly
without impacting existing functionality.
>
> I don't think a separate branch is necessary, @slfan1989 .
>
> These changes are designed to be transparent, especially now that we've
added a shortcut to avoid the subject manipulation for Java 21 and earlier, as
suggested by @szetszwo .
>
> IF this breaks anything, we can find and fix that faster once it's in
trunk.
>
> Any changes affecting Java 8/11 will be causght by the existing CI
processes, and we can also start work on setting up CI for Java 17/21/25 and
start working out any such issues.
>
> Users will alse have an easier time testing Hadoop with Java 21/25 in
their use cases once it's supported on trunk.
@stoty Thank you for your reply, and also for your efforts in driving the
Java 22+ upgrade. I hope the work goes smoothly, and I'll do my best to support
it.
>> A related question @slfan1989 :
>> What is current stance on dropping pre Java 17 support from trunk ?
>> That would allow freeing up CI resources, and start migrating off
problematic old component versions like Jetty 9.4.
From my understanding, the trunk branch will soon drop support for Java 8
and Java 11, and move forward with Java 17 as the new baseline for development.
We also plan to finalize the release scope of Hadoop 3.5 as soon as possible
and initiate the corresponding release process.
As for CI support for Java 21 and above, further discussion may be needed. I
plan to respond to the previous DISCUSS thread early next week and continue
driving the related efforts. In the meantime, input and suggestions from other
community members would be very welcome.
> Restore Subject propagation semantics for Java 22+
> --------------------------------------------------
>
> Key: HADOOP-19574
> URL: https://issues.apache.org/jira/browse/HADOOP-19574
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Istvan Toth
> Assignee: Istvan Toth
> Priority: Critical
> Labels: pull-request-available
>
> Java 22 breaks Subject propagation for new Threads (when SecurityManager is
> not enabled).
> Previously, the Subject set by Subject.doAs() / Subject.callAs()
> automatically propagated to any new Threads created (via new Thread(), not
> Executors).
> With JDK22, this is no longer the case, new Threads do NOT inherit the
> Subject.
> As Hadoop heavily relies on the original behavior, we somehow need to solve
> this problem.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
