[
https://issues.apache.org/jira/browse/BEAM-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470845#comment-17470845
]
Chamikara Madhusanka Jayalath edited comment on BEAM-13606 at 1/7/22, 7:31 PM:
-------------------------------------------------------------------------------
I see. Agree that a Beam fix is needed as well.
Does it actually set OK status for successful mutations ? If not successful
mutations will be indistinguishable from failed mutations with 'None' as the
return status.
was (Author: chamikara):
I see. Agree that a Beam fix is needed as well.
Does it actually, set OK status for successful mutations ? If not successful
mutations will be indistinguishable from failed mutations with 'None' as the
return status.
> bigtable io doesn't handle non-ok row mutations
> -----------------------------------------------
>
> Key: BEAM-13606
> URL: https://issues.apache.org/jira/browse/BEAM-13606
> Project: Beam
> Issue Type: Bug
> Components: io-py-gcp
> Reporter: Ning
> Assignee: Chamikara Madhusanka Jayalath
> Priority: P1
>
> bigtable io has no logic to retry row mutations for rows with non-ok return
> status (this includes None return value when bigtable suppresses retryable
> errors, details see BEAM-13602).
>
> To avoid data loss, the solution should be:
> # Retry for those retryable-failed row mutations;
> # Tagged output for those non-retryable-failed row mutations.
> Or clarify that the I/O doesn't handle failed row mutations in docstrings.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
