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-21 UTC."],[[["This webpage provides documentation for the `AppProfileConfig` class within the Google Cloud Bigtable C++ client library, covering versions from 2.11.0 up to the latest release candidate 2.37.0-rc."],["The `AppProfileConfig` class allows users to define the configuration for routing read and write requests within a Bigtable instance using different functions and constructors."],["Key functions include `set_ignore_warnings`, `set_description`, and `set_etag`, which allow for setting configuration properties of the app profile, as well as `as_proto`, which returns the configuration as the `CreateAppProfileRequest` proto."],["Static methods like `MultiClusterUseAny` and `SingleClusterRouting` are provided to create AppProfiles for multi-cluster routing or single-cluster routing, respectively, offering control over availability and consistency trade-offs."],["The page lists the version history for the `AppProfileConfig` class, offering links to previous documentation for each of the mentioned versions."]]],[]]
