damccorm opened a new issue, #21625: URL: https://github.com/apache/beam/issues/21625
From [https://github.com/apache/beam/pull/17404](https://github.com/apache/beam/pull/17404), it seems like the timestamp conversion has been made stricter, such that the pipeline only accepts timestamps in the form “2022-05-09T18:04:59Z”. Here are some formats that previously worked, but seem to no longer be accepted: “2022-05-09 18:04:59” “2022-05-09T18:04:59” “2022-05-09T18:04:59.739-07:00” Also from the same pull request, it seems to no longer accept integers in fields marked as floats Unexpected value :0, type: class java.lang.Integer. Table field name: a, type: FLOAT64 Are these the desired behaviors? It’s different from the behavior I’ve observed when using the Streaming Inserts method. Imported from Jira [BEAM-14528](https://issues.apache.org/jira/browse/BEAM-14528). Original Jira may contain additional context. Reported by: kkgcp. -- 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]
