Struct PartitionQueryRequest 

pub struct PartitionQueryRequest {
    pub param_types: Option<HashMap<String, Type>>,
    pub params: Option<HashMap<String, Value>>,
    pub partition_options: Option<PartitionOptions>,
    pub sql: Option<String>,
    pub transaction: Option<TransactionSelector>,
}

The request for PartitionQuery

Activities

This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).

• instances databases sessions partition query projects (request)

Fields

param_types: Option<HashMap<String, Type>>

It isn’t always possible for Cloud Spanner to infer the right SQL type from a JSON value. For example, values of type BYTES and values of type STRING both appear in params as JSON strings. In these cases, param_types can be used to specify the exact SQL type for some or all of the SQL query parameters. See the definition of Type for more information about SQL types.

params: Option<HashMap<String, Value>>

Parameter names and values that bind to placeholders in the SQL string. A parameter placeholder consists of the @ character followed by the parameter name (for example, @firstName). Parameter names can contain letters, numbers, and underscores. Parameters can appear anywhere that a literal value is expected. The same parameter name can be used more than once, for example: "WHERE id > @msg_id AND id < @msg_id + 100" It’s an error to execute a SQL statement with unbound parameters.

partition_options: Option<PartitionOptions>

Additional options that affect how many partitions are created.

sql: Option<String>

Required. The query request to generate partitions for. The request fails if the query isn’t root partitionable. For a query to be root partitionable, it needs to satisfy a few conditions. For example, if the query execution plan contains a distributed union operator, then it must be the first operator in the plan. For more information about other conditions, see Read data in parallel. The query request must not contain DML commands, such as INSERT, UPDATE, or DELETE. Use ExecuteStreamingSql with a PartitionedDml transaction for large, partition-friendly DML operations.

transaction: Option<TransactionSelector>

Read-only snapshot transactions are supported, read and write and single-use transactions are not.

Trait Implementations

impl Clone for PartitionQueryRequest

fn clone(&self) -> PartitionQueryRequest

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for PartitionQueryRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for PartitionQueryRequest

fn default() -> PartitionQueryRequest

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for PartitionQueryRequest

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for PartitionQueryRequest

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl RequestValue for PartitionQueryRequest