ConstExcept for empty batch requests described below, a batch operation contains two or more database operations explicitly submitted as separate operations in a single client call, protocol message, or database command.
Requests to batch APIs that contain only one operation SHOULD be modeled as single operations, not as batch operations.
A database call is not a batch operation solely because one operation accepts
multiple operands, such as keys, rows, documents, points, or other data elements,
including Redis MGET with
multiple keys.
In batch APIs that execute the same parameterized operation with parameter sets, each parameter set represents one database operation for determining whether the request is a batch operation. Requests with only one parameter set SHOULD be modeled as single operations, not as batch operations.
db.operation.batch.size SHOULD be set to the number of operations in the batch.
It SHOULD NOT be set for non-batch operations.
A request to execute a batch operation with no operations SHOULD also be treated
as a batch operation, and db.operation.batch.size SHOULD be set to 0.
The number of database operations included in a batch operation.