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-14 UTC."],[[["This document provides reference information for the `AppProfileConfig` class within the Google Cloud Bigtable C++ client library, including versions ranging from 2.11.0 to 2.37.0-rc, with 2.37.0-rc being the latest release candidate."],["The `AppProfileConfig` class is used to define how requests are routed within Bigtable, including configurations for multi-cluster or single-cluster routing, with the ability to set parameters such as the profile ID and cluster IDs."],["Key functionalities of `AppProfileConfig` include setting properties like description, ETag, and ignore warnings, as well as methods for converting the configuration to and from its underlying protocol buffer representation."],["There are two primary static methods available for configuring routing: `MultiClusterUseAny`, which routes requests to the nearest available cluster, and `SingleClusterRouting`, which routes all requests to a specified cluster."],["The `SingleClusterRouting` method can be configured to allow or disallow transactional writes based on whether or not `CheckAndMutateRow` and `ReadModifyWriteRow` are allowed."]]],[]]
