Data consistency levels
Cloud Datastore queries can deliver their results at either of two consistency levels:
- Strongly consistent queries guarantee the freshest results, but may take longer to complete.
- Eventually consistent queries generally run faster, but may occasionally return stale results.
In an eventually consistent query, the indexes used to gather the results are also accessed with eventual consistency. Consequently, such queries may sometimes return entities that no longer match the original query criteria, while strongly consistent queries are always transactionally consistent. See the article Transaction Isolation in App Engine for more information on how entities and indexes are updated.
Cloud Datastore query data consistency
Queries return their results with different levels of consistency guarantee, depending on the nature of the query:
- Ancestor queries (those within an entity group) are strongly consistent by default, but can instead be made eventually consistent by setting the Cloud Datastore read policy (see below).
- Non-ancestor queries are always eventually consistent.
Fetching an entity by key, which is also called "lookup by key", is strongly consistent.
Setting the Cloud Datastore read policy
To improve performance, you can set the Cloud Datastore read policy so that all reads and queries are eventually consistent. (The API also allows you to explicitly set a strong consistency policy, but this setting will have no practical effect, since non-ancestor queries are always eventually consistent regardless of policy.)You can also set the Cloud Datastore call deadline, which is the maximum time, in seconds, that the application will wait for Cloud Datastore to return a result before aborting with an error. The default deadline is 60 seconds; it is not currently possible to set it higher, but you can adjust it downward to ensure that a particular operation fails quickly (for instance, to return a faster response to the user). To set the Cloud Datastore read policy and call deadline in Python, you pass them as arguments to the
count()methods of class
GqlQuery. For example:
for result in Employee.all().run(limit=5, read_policy=db.EVENTUAL_CONSISTENCY, deadline=5): # Body of iterative loop
- Learn how to specify what a query returns and further control query results.
- Learn the common restrictions for queries on Cloud Datastore.
- Learn about query cursors, which allow an application to retrieve a query's results in convenient batches.
- Learn the basic syntax and structure of queries for Cloud Datastore.