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

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

                Author: ASF GitHub Bot
            Created on: 20/May/18 15:24
            Start Date: 20/May/18 15:24
    Worklog Time Spent: 10m 
      Work Description: calonso commented on issue #5341: [BEAM-4257] Increases 
BigQuery streaming error information
URL: https://github.com/apache/beam/pull/5341#issuecomment-390490319
 
 
   Thinking about this... Maybe you meant to say 'extend the information in the 
`TableRow`' instead of the retry policy?
   
   That could definitely be an option given that `TableRow` accepts storing 
anything, but I think it is clearer to actually use a class that holds all the 
information one may need to debug/inspect the error.
   
   Another idea I had is to create a new method in `WriteResult` class, 
something like `failedInsertsExtendedInfo` instead of changing the original 
`failedInserts`

----------------------------------------------------------------
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: 103748)
    Time Spent: 1h  (was: 50m)

> 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: 1h
>  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