From 84cfb0abdfabd8aa2f292fc0bb7e6deab50f87f1 Mon Sep 17 00:00:00 2001 From: John Fremlin Date: Wed, 23 Mar 2022 19:02:10 -0400 Subject: [PATCH] docs: explain mutate vs mutate_rows (#543) Thanks to Bora for spotting this! --- google/cloud/bigtable/batcher.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/google/cloud/bigtable/batcher.py b/google/cloud/bigtable/batcher.py index 950a198ef..3c23f4436 100644 --- a/google/cloud/bigtable/batcher.py +++ b/google/cloud/bigtable/batcher.py @@ -33,7 +33,7 @@ class MutationsBatcher(object): request. This class is not suited for usage in systems where each mutation - needs to guaranteed to be sent, since calling mutate may only result in an + must be guaranteed to be sent, since calling mutate may only result in an in-memory change. In a case of a system crash, any DirectRows remaining in memory will not necessarily be sent to the service, even after the completion of the mutate() method. @@ -105,7 +105,7 @@ def mutate(self, row): self.flush() def mutate_rows(self, rows): - """Add a row to the batch. If the current batch meets one of the size + """Add multiple rows to the batch. If the current batch meets one of the size limits, the batch is sent synchronously. For example: