Hi,
This is Kensuke. I’m responding on behalf of Kazuha (he is my colleague).
> Which runner are you using?
We are using the DirectRunner. As you suggested, we specified
“–add-opens=java.base/java.lang=ALL-UNNAMED” in the JVM invocation command
line, and it worked in the Java 21 environment. Spe
Hi,
Which runner are you using? If you are running on Dataflow runner, then
refer to this [1] and add
"--jdkAddOpenModules=java.base/java.lang=ALL-UNNAMED" to pipeline option.
If using direct runner, then add
"--add-opens=java.base/java.lang=ALL-UNNAMED" to JVM invocation command
line.
The same e
Hi, XQ
Thank you for your reply.
I tried to implement your suggestion by running `mvn compile exec:java
-Dexec.args="--add-opens=java.base/java.lang=ALL-UNNAMED"` or by editing a
plugin in the pom.xml as shown below.
However, I was unable to resolve this issue. As I am very new to Beam and
the OSS
Probably related to the strict encapsulation that is enforced with Java 21.
Use `--add-opens=java.base/java.lang=ALL-UNNAMED` as the JVM flag could be
a temporary workaround.
On Mon, Jun 3, 2024 at 3:04 AM 田中万葉 wrote:
> Hi all,
>
> I encountered an UnsupportedOperationException when using Java 2
Hi all,
I encountered an UnsupportedOperationException when using Java 21 and the
BigQuery Storage Write API in a Beam pipeline by using
".withMethod(BigQueryIO.Write.Method.STORAGE_WRITE_API));"
Having read issue #28120[1] and understanding that Beam version 2.52.0 or
later supports Java 21 as a
