Class Store.TxnPrewriteRequest.LockExtraData.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<Store.TxnPrewriteRequest.LockExtraData.Builder>
io.dingodb.store.Store.TxnPrewriteRequest.LockExtraData.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Store.TxnPrewriteRequest.LockExtraDataOrBuilder, Cloneable
Enclosing class:
Store.TxnPrewriteRequest.LockExtraData

public static final class Store.TxnPrewriteRequest.LockExtraData.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<Store.TxnPrewriteRequest.LockExtraData.Builder> implements Store.TxnPrewriteRequest.LockExtraDataOrBuilder
 The extra_data executor want to store in lock when doing prewrite
 if there is extra_data in a pessimistic lock, and no extra_data in the corresponding prewrite request, the
 extra_data in lock will not update, else the new extra_data will replace previous extra_data in lock
 
Protobuf type dingodb.pb.store.TxnPrewriteRequest.LockExtraData