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 outlines the various versions of the `AppProfileConfig` class within the Google Cloud Bigtable C++ library, ranging from version 2.11.0 to the latest release candidate 2.37.0-rc."],["The `AppProfileConfig` class can be used to create and configure an AppProfile, which determines how requests are routed to clusters in a Bigtable instance."],["The class provides constructors and functions to define settings like ignoring warnings, setting descriptions, and configuring the routing behavior of an app profile, through the `set_ignore_warnings`, `set_description`, and `set_etag` functions."],["There are two static functions, `MultiClusterUseAny` and `SingleClusterRouting`, that offer pre-configured app profiles, one for multi-cluster routing that prioritizes availability, and another for single-cluster routing that prioritizes consistency."],["`MultiClusterUseAny` routes requests to the nearest available cluster and `SingleClusterRouting` routes requests to a specific cluster with an option to allow or disallow transactional writes using the parameter `allow_transactional_writes`."]]],[]]
