[
https://issues.apache.org/jira/browse/BEAM-13606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ning updated BEAM-13606:
------------------------
Description:
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.
was: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)
> bigtable io doesn't retry for 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
> Priority: P2
>
> 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)
