damccorm opened a new issue, #21693: URL: https://github.com/apache/beam/issues/21693
Customer (F5) is working on migrating to the new Storage API support in Beam SDK and are facing issues in the latest Snapshot build. Today, in production, they are using the legacy streaming API and their pipeline works fine when they are mapping an incoming integer field to a BQ table field of type Float64. However, with the storage API, their pipeline is failing with the following error "Unexpected value :0, type: class java.lang.Integer. Table field name: a, type: FLOAT64" Customer considers this as a regression and is preventing them from going live with Storage API. Customer is planning on going live with Storage API end of July and would like to have this fixed in the 2.39.0 GA release. Imported from Jira [BEAM-14529](https://issues.apache.org/jira/browse/BEAM-14529). Original Jira may contain additional context. Reported by: yirutang. -- 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]
