Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: explain mutate vs mutate_rows #543

Merged
merged 2 commits into from Mar 23, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions google/cloud/bigtable/batcher.py
Expand Up @@ -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.
Expand Down Expand Up @@ -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:
Expand Down