Reference documentation and code samples for the Cloud Bigtable V2 Client class 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.
Generated from protobuf message google.bigtable.admin.v2.AppProfile.MultiClusterRoutingUseAny.RowAffinity
