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 document details the `AppProfileConfig` class for Google Cloud Bigtable, outlining its various versions and configurations."],["The latest release candidate is version 2.37.0-rc, with numerous other releases available, down to version 2.11.0."],["`AppProfileConfig` can be constructed using a `google::bigtable::admin::v2::CreateAppProfileRequest` and can set values for ignore warnings, descriptions, and etags."],["The document describes two routing options: `MultiClusterUseAny`, which routes requests to the nearest available cluster, and `SingleClusterRouting`, which directs all requests to a specified cluster."],["The class contains methods for configuring the AppProfile, such as `set_ignore_warnings`, `set_description`, and `set_etag`, as well as converting the configuration to a proto format using `as_proto`."]]],[]]
