Ryan van Huuksloot created FLINK-39172:
------------------------------------------
Summary: Flink Bash Scripts don't support the new yaml 1.2 syntax
when reading from config.yaml
Key: FLINK-39172
URL: https://issues.apache.org/jira/browse/FLINK-39172
Project: Flink
Issue Type: Bug
Components: Deployment / Scripts
Affects Versions: 2.2.0
Reporter: Ryan van Huuksloot
The config.sh reads from the config.yaml. The new support for yaml 1.2 isn't
supported in the shell scripts.
Here is the implementation:
[https://github.com/apache/flink/blob/657f4181968a1c2017dd3c91842ccf7c80241ff7/flink-dist/src/main/flink-bin/bin/config.sh#L104C1-L112]
Most configurations don't go through the configuration script so I assume that
is why it hasn't been an issue.
*Minimal Reproduction*
{code:java}
env:
java:
opts:
all: |+
--add-exports=java.base/sun.net.util=ALL-UNNAMED
--add-opens=java.base/java.lang=ALL-UNNAMED {code}
If you start a cluster and look at the java opts, they are not passed through.
You can use `ps aux` to check your java process.
However, if you do the following these java.opts exist when you startup the job
{code:java}
env.java.opts.all: "--add-exports=java.base/sun.net.util=ALL-UNNAMED
--add-opens=java.base/java.lang=ALL-UNNAMED" {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
