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

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

                Author: ASF GitHub Bot
            Created on: 19/May/18 06:01
            Start Date: 19/May/18 06:01
    Worklog Time Spent: 10m 
      Work Description: reuvenlax commented on issue #5341: [BEAM-4257] 
Increases BigQuery streaming error information
URL: https://github.com/apache/beam/pull/5341#issuecomment-390382315
 
 
   High-level thought: why do you need a new BigQueryInsertError class? Is 
there a reason why you can't simply extend the information in the retry policy?
   
   One issue with this PR is that it is backwards incompatible, meaning that 
current pipelines will have trouble with it. We generally don't make 
backwards-incompatible changes except across major Beam versions unfortunately.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


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

    Worklog Id:     (was: 103653)
    Time Spent: 40m  (was: 0.5h)

> Add error reason and table destination to BigQueryIO streaming failed inserts
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-4257
>                 URL: https://issues.apache.org/jira/browse/BEAM-4257
>             Project: Beam
>          Issue Type: Improvement
>          Components: io-java-gcp
>            Reporter: Carlos Alonso
>            Assignee: Carlos Alonso
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> When using `BigQueryIO.Write` and getting `WriteResult.getFailedInserts()` we 
> get a `PCollection<TableRow>` which is fine, but in order to properly work on 
> the errors downstream having extended information such as the `InsertError` 
> fields and the `TableReference` it was routed to would be really valuable.
>  
> My suggestion is to create a new object that contains all that information 
> and return a `PCollection` of those instead.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to