[GitHub] [beam] cozos commented on issue #22986: [Bug]: WriteToBigquery Deadletter pattern does not work with FILE_LOADS method

[GitBox <gi...@apache.org>]

cozos commented on issue #22986:
URL: https://github.com/apache/beam/issues/22986#issuecomment-1336681555

   To summarize what is happening:
   
   - I am calling `WriteToBigQuery` in a batch job (therefore `FILE_LOADS` strategy)
   - I am using Avro as the temp file format for performance reasons. Avro is the preferred format BQ Load Jobs as per the [ GCP docs](https://cloud.google.com/bigquery/docs/batch-loading-data)
   - I am also setting `insert_retry_strategy='RETRY_ON_TRANSIENT_ERROR'`
   
   Expected behavior:
   When writing an element to BigQuery, failed rows such as from schema mismatch should appear as `FailedRows` in the result tuple, which can then be used in a DLQ pattern such as [here](https://beam.apache.org/documentation/patterns/bigqueryio/)
   
   Actual behavior:
   Specifically for schema mismatch errors the job will simply fail on `fastavro.write` when writing records with bad schema.
   


-- 
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