Cloud Bigtable V2 Client - Class RowAffinity (2.5.0)

Version 2.5.0

• 2.6.1 (latest)
• 2.6.0
• 2.5.0
• 2.4.0
• 2.3.0
• 2.2.1
• 2.1.0
• 2.0.1
• 1.32.1
• 1.31.1
• 1.30.0
• 1.29.2
• 1.28.3
• 1.27.0
• 1.26.2
• 1.25.0
• 1.24.1
• 1.23.0
• 1.22.2
• 1.21.1
• 1.20.3

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

Namespace

Google \ Cloud \ Bigtable \ Admin \ V2 \ AppProfile \ MultiClusterRoutingUseAny

Methods

__construct

Constructor.

Parameter
Name	Description
data	array Optional. Data for populating the Message object.