[GitHub] [beam] DerRidda commented on issue #22733: [Feature Request]: Use unique id for Python BigQueryIO

["DerRidda (via GitHub)" <gi...@apache.org>]

DerRidda commented on issue #22733:
URL: https://github.com/apache/beam/issues/22733#issuecomment-1493863894

   > I think this is a non-issue, given this is fixed in Java. IIUC, because templates use only Java IOs under the hood (and the direction of templates seems to be to migrate to flex), a fix here should be unnecessary.
   
   I think this is a pronounced misinterpretation of the issue. The existing BigQuery IO transforms in the Beam SDK do not use Java at all, only the new Storage API based writer does that, so all unchanged existing code is expected to rely on code that has this issue.
   
   Furthermore while Flex templates exist and it seems to be a desire by the Dataflow maintainers for uses to migrate to them, the classic templates are still fully supported, keep being developed and no deprecation notice has been issued. At my job we have currently no desire to migrate to Flex templates as they solve 0 issues for us and would only introduce unwanted latency in our job orchestration.


-- 
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: github-unsubscribe@beam.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org