apache / apache/beam

Return ERROR details from apache_beam.io.gcp.bigquery.WriteToBigQuery failed inserts

Open
#20,362 0 comments 0 reactions 0 assignees View on GitHub
gcp improvement io P3 python
Dominant language
Java
Stars
8.7k
Forks
4.7k
Avg merge
1d 20h
Merged PRs (30d)
196

Description

In:
class BigQueryWriteFn(DoFn):
 - def _flush_batch(self, destination):
 
Return an additional pvalue.TaggedOutput with the detailed ERROR from failed insertion to BigQuery.
 
Today the error returns only the row (payload) of the error, like this:
```

// Return Statement
return [
pvalue.TaggedOutput(
BigQueryWriteFn.FAILED_ROWS,
GlobalWindows.windowed_value((destination,
row)))
for row in failed_rows
]

```

 
For error analysis it is super important to understand WHAT is causing the error.
In this same function, we only need to return the error from BigQuery in an additional pvalue.TaggedOutput:
 
```

// Function that captures the error
passed, errors = self.bigquery_wrapper.insert_rows(
project_id=table_reference.projectId,

dataset_id=table_reference.datasetId,
table_id=table_reference.tableId,
rows=rows,
insert_ids=insert_ids,
skip_invalid_rows=True)

```

The new return would look like this:
 
```

// new return statement
return [
pvalue.TaggedOutput(
BigQueryWriteFn.FAILED_ROWS,
GlobalWindows.windowed_value((destination,
row, error)))
for row in failed_rows
]
```

 Thank you!

Imported from Jira [BEAM-10640](https://issues.apache.org/jira/browse/BEAM-10640). Original Jira may contain additional context.
Reported by: leiterenato.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.