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