You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently when a BigQueryConnectException is thrown, the formatInsertAllErrors printer outputs some information about which rows failed and with what error. Unfortunately the end user cannot correlate these rows at all back to the actual message that failed to insert as I see it. We should propagate the offset information to this exception if possible and print it when this exception is thrown so that users get actionable information. From my understanding this would entail modifying the BigQueryWriter to work with lists of Tuple[Offset, InsertAllRequest.RowToInsert] or some similar structure instead of just the rows, but I would appreciate guidance on how to go about this.
The text was updated successfully, but these errors were encountered:
Currently when a
BigQueryConnectException
is thrown, theformatInsertAllErrors
printer outputs some information about which rows failed and with what error. Unfortunately the end user cannot correlate these rows at all back to the actual message that failed to insert as I see it. We should propagate the offset information to this exception if possible and print it when this exception is thrown so that users get actionable information. From my understanding this would entail modifying theBigQueryWriter
to work with lists of Tuple[Offset, InsertAllRequest.RowToInsert] or some similar structure instead of just the rows, but I would appreciate guidance on how to go about this.The text was updated successfully, but these errors were encountered: