Abacn commented on issue #25567: URL: https://github.com/apache/beam/issues/25567#issuecomment-1441993394
I understand the current behavior is more like a promoting/casting INT -> LONG (and if also happens on other types) to align the avro schema to the final BigQuery table destination schema. If the consideration is cost (INT uses smaller space than LONG), BigQuery storage API is more promising (though the work is ongoing). CC: @reuvenlax -- 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]
