You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After upgrading Apache Beam to the today's latest version 2.48.0, we encountered some issues with our tests. All tests were failing because of this following error:
Caused by: java.lang.IllegalArgumentException: org.apache.beam.model.Function$SchemaCodeGen$9JxP0J5v must be defined in the same package as org.apache.beam.vendor.guava.v26_0_jre.com.google.common.base.Function
It only happens when you have a nested schema. If we remove the nested schema it works fine.
I created this repository beam-schema-bug that you can run with DirectRunner to reproduce the issue.
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components
Component: Python SDK
Component: Java SDK
Component: Go SDK
Component: Typescript SDK
Component: IO connector
Component: Beam examples
Component: Beam playground
Component: Beam katas
Component: Website
Component: Spark Runner
Component: Flink Runner
Component: Samza Runner
Component: Twister2 Runner
Component: Hazelcast Jet Runner
Component: Google Cloud Dataflow Runner
The text was updated successfully, but these errors were encountered:
The same problem (however with different package prefix for Function) occurs with custom generated protobuf classes, e.g.:
org.apache.beam.sdk.Pipeline$PipelineExecutionException: java.lang.IllegalArgumentException: com.my.pacakge.with.proto.Function$SchemaCodeGen$bWrbfTA2 must be defined in the same package as org.apache.beam.vendor.guava.v26_0_jre.com.google.common.base.Function
Version 2.47 works, so the bug was introduced in 2.48
I have the same issue. I've generated classes from an Avro schema using avro-compiler at build time and Apache Beam in version 2.48.0 can't handle them properly.
What happened?
After upgrading Apache Beam to the today's latest version 2.48.0, we encountered some issues with our tests. All tests were failing because of this following error:
It only happens when you have a nested schema. If we remove the nested schema it works fine.
I created this repository beam-schema-bug that you can run with DirectRunner to reproduce the issue.
Issue Priority
Priority: 1 (data loss / total loss of function)
Issue Components
The text was updated successfully, but these errors were encountered: