ahmedabu98 opened a new issue, #33917: URL: https://github.com/apache/beam/issues/33917
### What would you like to happen? Currently, when useBeamSchema() is set, we just infer the Schema from the incoming data schema: https://github.com/apache/beam/blob/99e7bbf348c9e2903773e21cd063625f21e84238/sdks/java/io/google-cloud-platform/src/main/java/org/apache/beam/sdk/io/gcp/bigquery/BigQueryIO.java#L3621 We should first be checking if the dynamic destinations object has a schema to pull from. Doing this will allow us to set `useBeamSchema()` for portable BigQueryIO scenarios (cross-language, ManagedIO) and skip converting to TableRow. Essentially going from - Beam Row --> TableRow --> proto to - Beam Row --> proto Hopefully will give us meaningful performance improvements ### Issue Priority Priority: 2 (default / most feature requests should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [x] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [x] Component: IO connector - [ ] Component: Beam YAML - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Infrastructure - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
