[jira] [Commented] (BEAM-13606) bigtable io doesn't handle non-ok row mutations

["Ahmet Altay (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/BEAM-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470324#comment-17470324 ] 

Ahmet Altay commented on BEAM-13606:
------------------------------------

[~chamikara] [~kerrydc] - Would it be possible to verify if there is a risk of data loss in this scenario? If that is the case, we need to fix it sooner than later. 

Do we have an owner for bigtable IO from the bigtable people?

> 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)