Skip to content

Commit 3945ca9

Browse files
Chris Rossiandrewsg
andauthored
docs: correct documentation for GlobalCache (#565)
Had mistakenly written that non-strict behavior occurs when `strict_read` or `strict_write` are `True`, when it should have said when they are `False`. Closes #563. Co-authored-by: Andrew Gorcester <[email protected]>
1 parent 8934369 commit 3945ca9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

packages/google-cloud-ndb/google/cloud/ndb/global_cache.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,10 +47,10 @@ class GlobalCache(object):
4747
implementations, as some specialized knowledge is required.
4848
4949
Attributes:
50-
strict_read (bool): If :data:`True`, transient errors that occur as part of a
50+
strict_read (bool): If :data:`False`, transient errors that occur as part of a
5151
entity lookup operation will be logged as warnings but not raised to the
5252
application layer.
53-
strict_write (bool): If :data:`True`, transient errors that occur as part of
53+
strict_write (bool): If :data:`False`, transient errors that occur as part of
5454
a put or delete operation will be logged as warnings, but not raised to the
5555
application layer. Setting this to :data:`True` somewhat increases the risk
5656
that other clients might read stale data from the cache.

0 commit comments

Comments
 (0)