Optional
applyApply policy. For more information, see ApplyPolicy
Optional
batchBatch policy. For more information, see BasePolicy
Optional
batchBatch parent write policy. For more information, see BatchPolicy
Optional
infoInfo policy. For more information, see InfoPolicy
Optional
operateOperate policy. For more information, see OperatePolicy
Optional
queryQuery policy. For more information, see QueryPolicy
Optional
readRead policy. For more information, see ReadPolicy
Optional
removeRemove policy. For more information, see RemovePolicy
Optional
scanScan policy. For more information, see ScanPolicy
Optional
writeWrite policy. For more information, see WritePolicy
Global client policies.
Remarks
The configuration defines default policies for the application. Policies define the behavior of the client, which can be global for all uses of a single type of command, or local to a single use of an command.
Each database command accepts a policy for that command as an argument. This is considered a local policy, and is a single use policy. This local policy supersedes any global policy defined.
If a value of the policy is not defined, then the rule is to fallback to the global policy for that command. If the global policy for that command is undefined, then the global default value will be used.
If you find that you have behavior that you want every use of an command to utilize, then you can specify the default policy as Config#policies.
For example, the Client#put command takes a WritePolicy parameter. If you find yourself setting the WritePolicy#key policy value for every call to Client.put, then you may find it beneficial to set the global WritePolicy in Config#policies, which all commands will use.
Example: Setting a default <code>key</code> policy for all write commands