Uses of Class
io.dingodb.store.Store.TxnPessimisticLockRequest.Builder
Packages that use Store.TxnPessimisticLockRequest.Builder
-
Uses of Store.TxnPessimisticLockRequest.Builder in io.dingodb.store
Methods in io.dingodb.store that return Store.TxnPessimisticLockRequest.BuilderModifier and TypeMethodDescriptionStore.TxnPessimisticLockRequest.Builder.addAllMutations(Iterable<? extends Store.Mutation> values) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.addMutations(int index, Store.Mutation value) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.addMutations(int index, Store.Mutation.Builder builderForValue) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.addMutations(Store.Mutation value) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.addMutations(Store.Mutation.Builder builderForValue) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) Store.TxnPessimisticLockRequest.Builder.clear()Store.TxnPessimisticLockRequest.Builder.clearContext().dingodb.pb.store.Context context = 2;Store.TxnPessimisticLockRequest.Builder.clearField(com.google.protobuf.Descriptors.FieldDescriptor field) Store.TxnPessimisticLockRequest.Builder.clearForUpdateTs()Each locking command in a pessimistic transaction has its own timestamp oracle.Store.TxnPessimisticLockRequest.Builder.clearLockTtl()the lock's ttl is timestamp in milisecond, it's the absolute timestamp when the lock is expired.Store.TxnPessimisticLockRequest.Builder.clearMutations()In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof) Store.TxnPessimisticLockRequest.Builder.clearPrimaryLock()bytes primary_lock = 4;Store.TxnPessimisticLockRequest.Builder.clearRequestInfo().dingodb.pb.common.RequestInfo request_info = 1;Store.TxnPessimisticLockRequest.Builder.clearReturnValues()If it is true, store will return values of the keys if no error, so executor can cache the values for later read in the same transaction.Store.TxnPessimisticLockRequest.Builder.clearStartTs()uint64 start_ts = 5;Store.TxnPessimisticLockRequest.Builder.clone()Store.TxnPessimisticLockRequest.Builder.mergeContext(Store.Context value) .dingodb.pb.store.Context context = 2;Store.TxnPessimisticLockRequest.Builder.mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) Store.TxnPessimisticLockRequest.Builder.mergeFrom(com.google.protobuf.Message other) Store.TxnPessimisticLockRequest.Builder.mergeFrom(Store.TxnPessimisticLockRequest other) Store.TxnPessimisticLockRequest.Builder.mergeRequestInfo(Common.RequestInfo value) .dingodb.pb.common.RequestInfo request_info = 1;Store.TxnPessimisticLockRequest.Builder.mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) Store.TxnPessimisticLockRequest.newBuilder()Store.TxnPessimisticLockRequest.newBuilder(Store.TxnPessimisticLockRequest prototype) Store.TxnPessimisticLockRequest.newBuilderForType()protected Store.TxnPessimisticLockRequest.BuilderStore.TxnPessimisticLockRequest.newBuilderForType(com.google.protobuf.GeneratedMessageV3.BuilderParent parent) Store.TxnPessimisticLockRequest.Builder.removeMutations(int index) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.setContext(Store.Context value) .dingodb.pb.store.Context context = 2;Store.TxnPessimisticLockRequest.Builder.setContext(Store.Context.Builder builderForValue) .dingodb.pb.store.Context context = 2;Store.TxnPessimisticLockRequest.Builder.setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value) Store.TxnPessimisticLockRequest.Builder.setForUpdateTs(long value) Each locking command in a pessimistic transaction has its own timestamp oracle.Store.TxnPessimisticLockRequest.Builder.setLockTtl(long value) the lock's ttl is timestamp in milisecond, it's the absolute timestamp when the lock is expired.Store.TxnPessimisticLockRequest.Builder.setMutations(int index, Store.Mutation value) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.setMutations(int index, Store.Mutation.Builder builderForValue) In this case every `Op` of the mutations must be `PessimisticLock`.Store.TxnPessimisticLockRequest.Builder.setPrimaryLock(com.google.protobuf.ByteString value) bytes primary_lock = 4;Store.TxnPessimisticLockRequest.Builder.setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value) Store.TxnPessimisticLockRequest.Builder.setRequestInfo(Common.RequestInfo value) .dingodb.pb.common.RequestInfo request_info = 1;Store.TxnPessimisticLockRequest.Builder.setRequestInfo(Common.RequestInfo.Builder builderForValue) .dingodb.pb.common.RequestInfo request_info = 1;Store.TxnPessimisticLockRequest.Builder.setReturnValues(boolean value) If it is true, store will return values of the keys if no error, so executor can cache the values for later read in the same transaction.Store.TxnPessimisticLockRequest.Builder.setStartTs(long value) uint64 start_ts = 5;Store.TxnPessimisticLockRequest.Builder.setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields) Store.TxnPessimisticLockRequest.toBuilder()