[
https://issues.apache.org/jira/browse/BEAM-13606?focusedWorklogId=722573&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-722573
]
ASF GitHub Bot logged work on BEAM-13606:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Feb/22 03:36
Start Date: 08/Feb/22 03:36
Worklog Time Spent: 10m
Work Description: chamikaramj commented on pull request #16751:
URL: https://github.com/apache/beam/pull/16751#issuecomment-1032180920
Run Python 3.8 PostCommit
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 722573)
Time Spent: 2h (was: 1h 50m)
> 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
> Fix For: 2.37.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> 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)
