Create an AppProfile that uses multi-cluster routing.
Read/write requests are routed to the nearest cluster in the instance, and will fail over to the nearest cluster that is available in the event of transient errors or delays. Clusters in a region are considered equidistant. Choosing this option sacrifices read-your-writes consistency to improve availability.
Parameters
Name
Description
profile_id
std::string
The unique name of the AppProfile.
cluster_ids
std::vector< std::string >
The set of clusters to route to. The order is ignored; clusters will be tried in order of distance. If left empty, all clusters are eligible.
Create an AppProfile that uses single cluster routing.
Unconditionally routes all read/write requests to a specific cluster. This option preserves read-your-writes consistency but does not improve availability.
Parameters
Name
Description
profile_id
std::string
The unique name of the AppProfile.
cluster_id
std::string
The cluster to which read/write requests are routed.
allow_transactional_writes
bool
Whether or not CheckAndMutateRow and ReadModifyWriteRow requests are allowed by this app profile. It is unsafe to send these requests to the same table/row/column in multiple clusters.
[[["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 2025-03-05 UTC."],[[["The content provides a comprehensive list of available versions for `AppProfileConfig`, ranging from the latest release candidate (2.37.0-rc) down to version 2.11.0, and each one of them links to its documentation."],["`AppProfileConfig` is used to specify the initial configuration when setting up an application profile within the Bigtable system, with a constructor that takes a `google::bigtable::admin::v2::CreateAppProfileRequest`."],["Several functions are available to configure the `AppProfileConfig` object, such as `set_ignore_warnings`, `set_description`, and `set_etag`, each of which returns an `AppProfileConfig&` allowing method chaining."],["The content describes two static methods, `MultiClusterUseAny` and `SingleClusterRouting`, which allow to create different AppProfile routing strategies, either routing requests to the nearest available cluster or to a specific cluster, respectively."],["The `MultiClusterUseAny` and `SingleClusterRouting` methods allow setting up the routing behavior based on a profile id, and either an array of cluster id's or a single cluster ID respectively."]]],[]]
