Repository navigation
Expose consistency setting in LocalGcdHelper #639
Description
Activity
This consistency setting should be used in DatastoreTest, since we use a query to get and delete all entities between tests.
- added 2 commits that reference this issue
on Jun 23, 2022 - added a commit that references this issue
on Sep 15, 2022 - added 2 commits that reference this issue
on Feb 1, 2023 - added a commit that references this issue
on Dec 22, 2025 - added a commit that references this issue
on Jan 6, 2026 - added a commit that references this issue
on Jan 22, 2026 - added a commit that references this issue
on Feb 24, 2026 - added a commit that references this issue
on Mar 11, 2026 - added a commit that references this issue
on Mar 12, 2026 - added a commit that references this issue
on Mar 23, 2026 - added 2 commits that reference this issue
on Mar 30, 2026 - added 2 commits that reference this issue
on Apr 1, 2026 - added a commit that references this issue
on Jul 13, 2026
The default is 0.9, but it's often useful to set it to 1.0 for test utility methods (i.e. clearing all entities using a non-ancestor query in between unit tests).
This can be set in LocalGcdHelper.startGcd(..) using the following option:
--consistency=...
The fraction of job application attempts that will succeed, with 0.0 resulting in no attempts succeeding, and 1.0 resulting in all attempts succeeding. Defaults to 0.9. Note that setting this to 1.0 may mask incorrect assumptions about the consistency of non-ancestor queries; non-ancestor queries are eventually consistent.