You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@tez.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2026/06/22 16:03:00 UTC

[jira] [Commented] (TEZ-4545) Add add-opens flag to container launch commands on JDK17 nodes

    [ https://issues.apache.org/jira/browse/TEZ-4545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18090659#comment-18090659 ] 

László Bodor commented on TEZ-4545:
-----------------------------------

considering minimum JDK21 compatibility from 1.0.0, we're not about to support dynamic container launch opts in a backward-compatible way, this can be resolved I think

> Add add-opens flag to container launch commands on JDK17 nodes
> --------------------------------------------------------------
>
>                 Key: TEZ-4545
>                 URL: https://issues.apache.org/jira/browse/TEZ-4545
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Bilwa S T
>            Assignee: Bilwa S T
>            Priority: Major
>
> To allow containers to launch on JDK17 nodes the add-opens flag should be added to the container launch commands if the node has JDK17+, and it shouldn't on previous JDKs. This behaviour should be configurable.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)