This configuration can be passed to most datastore calls using the
'config=...' argument.
Args
deadline
Optional deadline; default None (which means the
system default deadline will be used, typically 5 seconds).
on_completion
Optional callback function; default None. If
specified, it will be called with a UserRPC object as argument
when an RPC completes.
read_policy
Optional read policy; set to EVENTUAL_CONSISTENCY to
enable eventually consistent reads (i.e. reads that may be
satisfied from an older version of the datastore in some cases).
The default read policy may have to wait until in-flight
transactions are committed.
**kwds
Other keyword arguments as long as they are supported by
datastore_rpc.Configuration().
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2022-09-30 UTC."],[[["The `CreateConfig` function creates a configuration object for customizing datastore calls."],["This configuration can be applied to most datastore calls using the `config` argument."],["You can set optional parameters like `deadline`, `on_completion`, and `read_policy` to customize the datastore call behavior."],["The `read_policy` allows you to set eventual consistency for reads, potentially retrieving older data versions."],["It returns an instance of `datastore_rpc.Configuration`, which is then used in the aforementioned `config` argument."]]],[]]
View source on GitHub