<?php
# Generated by the protocol buffer compiler.  DO NOT EDIT!
# source: google/bigtable/admin/v2/instance.proto

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

use Google\Protobuf\Internal\GPBType;
use Google\Protobuf\Internal\RepeatedField;
use Google\Protobuf\Internal\GPBUtil;

/**
 * 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 <code>google.bigtable.admin.v2.AppProfile.MultiClusterRoutingUseAny.RowAffinity</code>
 */
class RowAffinity extends \Google\Protobuf\Internal\Message
{

    /**
     * Constructor.
     *
     * @param array $data {
     *     Optional. Data for populating the Message object.
     *
     * }
     */
    public function __construct($data = NULL) {
        \GPBMetadata\Google\Bigtable\Admin\V2\Instance::initOnce();
        parent::__construct($data);
    }

}

// Adding a class alias for backwards compatibility with the previous class name.
class_alias(RowAffinity::class, \Google\Cloud\Bigtable\Admin\V2\AppProfile_MultiClusterRoutingUseAny_RowAffinity::class);

