Class AppProfile.DataBoostIsolationReadOnly.Builder

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

public static final class AppProfile.DataBoostIsolationReadOnly.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<AppProfile.DataBoostIsolationReadOnly.Builder> implements AppProfile.DataBoostIsolationReadOnlyOrBuilder
 Data Boost is a serverless compute capability that lets you run
 high-throughput read jobs on your Bigtable data, without impacting the
 performance of the clusters that handle your application traffic.
 Currently, Data Boost exclusively supports read-only use-cases with
 single-cluster routing.

 Data Boost reads are only guaranteed to see the results of writes that
 were written at least 30 minutes ago. This means newly written values may
 not become visible for up to 30m, and also means that old values may
 remain visible for up to 30m after being deleted or overwritten. To
 mitigate the staleness of the data, users may either wait 30m, or use
 CheckConsistency.
 
Protobuf type google.bigtable.admin.v2.AppProfile.DataBoostIsolationReadOnly