[ 
https://issues.apache.org/jira/browse/BEAM-14383?focusedWorklogId=768587&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-768587
 ]

ASF GitHub Bot logged work on BEAM-14383:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/May/22 16:50
            Start Date: 10/May/22 16:50
    Worklog Time Spent: 10m 
      Work Description: pabloem commented on PR #17601:
URL: https://github.com/apache/beam/pull/17601#issuecomment-1122640104

   Run Python 3.8 PostCommit




Issue Time Tracking
-------------------

    Worklog Id:     (was: 768587)
    Time Spent: 5h  (was: 4h 50m)

> Improve "FailedRows" errors returned by beam.io.WriteToBigQuery
> ---------------------------------------------------------------
>
>                 Key: BEAM-14383
>                 URL: https://issues.apache.org/jira/browse/BEAM-14383
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-py-gcp
>            Reporter: Oskar Firlej
>            Priority: P2
>             Fix For: 2.39.0
>
>          Time Spent: 5h
>  Remaining Estimate: 0h
>
> `WriteToBigQuery` pipeline returns `errors` when trying to insert rows that 
> do not match the BigQuery table schema. `errors` is a dictionary that 
> cointains one `FailedRows` key. `FailedRows` is a list of tuples where each 
> tuple has two elements: BigQuery table name and the row that didn't match the 
> schema.
> This can be verified by running the `BigQueryIO deadletter pattern` 
> https://beam.apache.org/documentation/patterns/bigqueryio/
> Using this approach I can print the failed rows in a pipeline. When running 
> the job, logger simultaneously prints out the reason why the rows were 
> invalid. The reason should also be included in the tuple in addition to the 
> BigQuery table and the raw row. This way next pipeline could process both the 
> invalid row and the reason why it is invalid.
> During my reasearch i found a couple of alternate solutions, but i think they 
> are more complex than they need to be. Thats why i explored the beam source 
> code and found the solution to be an easy and simple change.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

Reply via email to