Class AppProfile.MultiClusterRoutingUseAny.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<AppProfile.MultiClusterRoutingUseAny.Builder>
com.google.bigtable.admin.v2.AppProfile.MultiClusterRoutingUseAny.Builder
All Implemented Interfaces:
AppProfile.MultiClusterRoutingUseAnyOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable
Enclosing class:
AppProfile.MultiClusterRoutingUseAny

public static final class AppProfile.MultiClusterRoutingUseAny.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<AppProfile.MultiClusterRoutingUseAny.Builder> implements AppProfile.MultiClusterRoutingUseAnyOrBuilder
 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.
 
Protobuf type google.bigtable.admin.v2.AppProfile.MultiClusterRoutingUseAny