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."],[[["The provided content outlines the `AppProfileConfig` class within the Google Cloud Bigtable C++ library, detailing its various versions and functionalities."],["`AppProfileConfig` allows configuration of application profiles, with methods to set parameters like description, etag, and ignore warnings, and the option to generate the profile request in the proto buffer format."],["The class provides static methods for configuring multi-cluster routing (`MultiClusterUseAny`) and single-cluster routing (`SingleClusterRouting`) for Bigtable access."],["Multi-cluster routing in `MultiClusterUseAny` optimizes for availability by routing requests to the nearest cluster and failing over as needed, while sacrificing read-your-writes consistency."],["Single cluster routing, via `SingleClusterRouting`, provides read-your-writes consistency by directing requests to a specified cluster, but does not improve availability, and transactional writes can be allowed or disallowed."]]],[]]
