public sealed class AppProfile.Types.MultiClusterRoutingUseAny.Types.RowAffinity : IMessage<AppProfile.Types.MultiClusterRoutingUseAny.Types.RowAffinity>, IEquatable<AppProfile.Types.MultiClusterRoutingUseAny.Types.RowAffinity>, IDeepCloneable<AppProfile.Types.MultiClusterRoutingUseAny.Types.RowAffinity>, IBufferMessage, IMessage
Reference documentation and code samples for the Google Cloud Bigtable Administration v2 API class AppProfile.Types.MultiClusterRoutingUseAny.Types.RowAffinity.
If enabled, Bigtable will route the request based on the row key of the
request, rather than randomly. Instead, each row key will be assigned
to a cluster, and will stick to that cluster. If clusters are added or
removed, then this may affect which row keys stick to which clusters.
To avoid this, users can use a cluster group to specify which clusters
are to be used. In this case, new clusters that are not a part of the
cluster group will not be routed to, and routing will be unaffected by
the new cluster. Moreover, clusters specified in the cluster group cannot
be deleted unless removed from the cluster group.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-08 UTC."],[[["\u003cp\u003eThis webpage provides reference documentation for the \u003ccode\u003eAppProfile.Types.MultiClusterRoutingUseAny.Types.RowAffinity\u003c/code\u003e class within the Google Cloud Bigtable Administration v2 API.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eRowAffinity\u003c/code\u003e class, which implements interfaces like \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, and \u003ccode\u003eIDeepCloneable\u003c/code\u003e, allows for routing requests based on row keys to specific clusters in Bigtable.\u003c/p\u003e\n"],["\u003cp\u003eThe content provides a history of various versions of this API class, ranging from 3.24.0 (latest) down to version 2.4.0.\u003c/p\u003e\n"],["\u003cp\u003eIt mentions that using a cluster group with \u003ccode\u003eRowAffinity\u003c/code\u003e can help maintain routing consistency when adding or removing clusters, preventing unintended rerouting of row keys.\u003c/p\u003e\n"],["\u003cp\u003eThe webpage mentions the \u003ccode\u003eRowAffinity\u003c/code\u003e class has two constructors, one default and one that accepts another \u003ccode\u003eRowAffinity\u003c/code\u003e object as a parameter.\u003c/p\u003e\n"]]],[],null,[]]
