Package io.dingodb.store

Interface Store.TxnPrewriteResponseOrBuilder

All Superinterfaces:
com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder
All Known Implementing Classes:
Store.TxnPrewriteResponse, Store.TxnPrewriteResponse.Builder
Enclosing class:
Store
public static interface Store.TxnPrewriteResponseOrBuilder extends com.google.protobuf.MessageOrBuilder

  • Method Details

    • hasResponseInfo

      boolean hasResponseInfo()
       response info
      .dingodb.pb.common.ResponseInfo response_info = 1;
      Returns:
      Whether the responseInfo field is set.

    • getResponseInfo

      Common.ResponseInfo getResponseInfo()
       response info
      .dingodb.pb.common.ResponseInfo response_info = 1;
      Returns:
      The responseInfo.

    • getResponseInfoOrBuilder

      Common.ResponseInfoOrBuilder getResponseInfoOrBuilder()
       response info
      .dingodb.pb.common.ResponseInfo response_info = 1;

    • hasError

      boolean hasError()
       error code
      .dingodb.pb.error.Error error = 2;
      Returns:
      Whether the error field is set.

    • getError

      ErrorOuterClass.Error getError()
       error code
      .dingodb.pb.error.Error error = 2;
      Returns:
      The error.

    • getErrorOrBuilder

      ErrorOuterClass.ErrorOrBuilder getErrorOrBuilder()
       error code
      .dingodb.pb.error.Error error = 2;

    • getTxnResultList

      List<Store.TxnResultInfo> getTxnResultList()
       for prewrite, txn_result will be one of the following:
 1. LockInfo: prewrite meet a lock and can't proceed, the lock is returned
 2. WriteConflict: Write conflict with key which is already written after start_ts
    2.1 Optimistic: in optimistic transactions.
    2.2 SelfRolledBack: the transaction itself has been rolled back when it tries to prewrite.
 3. otherwise, txn_result is empty
 for success prewrite, txn_result is empty
 for failure prewrite, txn_result is not empty
 if there is a WriteConflict in txn_result, client should backoff or cleanup the lock then retry
      repeated .dingodb.pb.store.TxnResultInfo txn_result = 3;

    • getTxnResult

      Store.TxnResultInfo getTxnResult(int index)
       for prewrite, txn_result will be one of the following:
 1. LockInfo: prewrite meet a lock and can't proceed, the lock is returned
 2. WriteConflict: Write conflict with key which is already written after start_ts
    2.1 Optimistic: in optimistic transactions.
    2.2 SelfRolledBack: the transaction itself has been rolled back when it tries to prewrite.
 3. otherwise, txn_result is empty
 for success prewrite, txn_result is empty
 for failure prewrite, txn_result is not empty
 if there is a WriteConflict in txn_result, client should backoff or cleanup the lock then retry
      repeated .dingodb.pb.store.TxnResultInfo txn_result = 3;

    • getTxnResultCount

      int getTxnResultCount()
       for prewrite, txn_result will be one of the following:
 1. LockInfo: prewrite meet a lock and can't proceed, the lock is returned
 2. WriteConflict: Write conflict with key which is already written after start_ts
    2.1 Optimistic: in optimistic transactions.
    2.2 SelfRolledBack: the transaction itself has been rolled back when it tries to prewrite.
 3. otherwise, txn_result is empty
 for success prewrite, txn_result is empty
 for failure prewrite, txn_result is not empty
 if there is a WriteConflict in txn_result, client should backoff or cleanup the lock then retry
      repeated .dingodb.pb.store.TxnResultInfo txn_result = 3;

    • getTxnResultOrBuilderList

      List<? extends Store.TxnResultInfoOrBuilder> getTxnResultOrBuilderList()
       for prewrite, txn_result will be one of the following:
 1. LockInfo: prewrite meet a lock and can't proceed, the lock is returned
 2. WriteConflict: Write conflict with key which is already written after start_ts
    2.1 Optimistic: in optimistic transactions.
    2.2 SelfRolledBack: the transaction itself has been rolled back when it tries to prewrite.
 3. otherwise, txn_result is empty
 for success prewrite, txn_result is empty
 for failure prewrite, txn_result is not empty
 if there is a WriteConflict in txn_result, client should backoff or cleanup the lock then retry
      repeated .dingodb.pb.store.TxnResultInfo txn_result = 3;

    • getTxnResultOrBuilder

      Store.TxnResultInfoOrBuilder getTxnResultOrBuilder(int index)
       for prewrite, txn_result will be one of the following:
 1. LockInfo: prewrite meet a lock and can't proceed, the lock is returned
 2. WriteConflict: Write conflict with key which is already written after start_ts
    2.1 Optimistic: in optimistic transactions.
    2.2 SelfRolledBack: the transaction itself has been rolled back when it tries to prewrite.
 3. otherwise, txn_result is empty
 for success prewrite, txn_result is empty
 for failure prewrite, txn_result is not empty
 if there is a WriteConflict in txn_result, client should backoff or cleanup the lock then retry
      repeated .dingodb.pb.store.TxnResultInfo txn_result = 3;

    • getKeysAlreadyExistList

      List<Store.AlreadyExist> getKeysAlreadyExistList()
       if there is PutIfAbsent in mutation, and if there is key conflict, the conflict key will be returned
      repeated .dingodb.pb.store.AlreadyExist keys_already_exist = 4;

    • getKeysAlreadyExist

      Store.AlreadyExist getKeysAlreadyExist(int index)
       if there is PutIfAbsent in mutation, and if there is key conflict, the conflict key will be returned
      repeated .dingodb.pb.store.AlreadyExist keys_already_exist = 4;

    • getKeysAlreadyExistCount

      int getKeysAlreadyExistCount()
       if there is PutIfAbsent in mutation, and if there is key conflict, the conflict key will be returned
      repeated .dingodb.pb.store.AlreadyExist keys_already_exist = 4;

    • getKeysAlreadyExistOrBuilderList

      List<? extends Store.AlreadyExistOrBuilder> getKeysAlreadyExistOrBuilderList()
       if there is PutIfAbsent in mutation, and if there is key conflict, the conflict key will be returned
      repeated .dingodb.pb.store.AlreadyExist keys_already_exist = 4;

    • getKeysAlreadyExistOrBuilder

      Store.AlreadyExistOrBuilder getKeysAlreadyExistOrBuilder(int index)
       if there is PutIfAbsent in mutation, and if there is key conflict, the conflict key will be returned
      repeated .dingodb.pb.store.AlreadyExist keys_already_exist = 4;

    • getOnePcCommitTs

      long getOnePcCommitTs()
       When the transaction is successfully committed with 1PC protocol, this
 field will be set to the commit ts of the transaction. Otherwise, if dingo-store
 failed to commit it with 1PC or the transaction is not 1PC, the value will
 be 0.
      int64 one_pc_commit_ts = 5;
      Returns:
      The onePcCommitTs.

    • getMinCommitTs

      long getMinCommitTs()
       0 if the min_commit_ts is not ready or any other reason that async
 commit cannot proceed. The client can then fallback to normal way to
 continue committing the transaction if prewrite are all finished.
      uint64 min_commit_ts = 6;
      Returns:
      The minCommitTs.