NOTE: This functions exists for backwards compatibility. Please use
create_config() instead. NOTE: the latter uses on_completion,
which is a function taking an argument, wherease create_rpc uses
callback which is a function without arguments.
Args
deadline
float, deadline for calls in seconds.
callback
callable, a callback triggered when this rpc completes,
accepts one argument: the returned rpc.
read_policy
flag, set to EVENTUAL_CONSISTENCY to enable eventually
consistent reads
[[["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."],[[["`create_rpc` is a function used for configuring datastore calls, but it's recommended to use `create_config` instead for new implementations."],["The `deadline` argument specifies the timeout in seconds for datastore calls."],["The `callback` argument, when provided, is a function that gets called when the RPC is completed, and it does not take in arguments."],["The `read_policy` argument allows you to choose between `STRONG_CONSISTENCY` (default) and `EVENTUAL_CONSISTENCY`."],["The function returns a `datastore.DatastoreRPC` object."]]],[]]
View source on GitHub