d8bd9fc7b3
Summary: This PR has two commits: 1. Modify the code to allow different Lock Managers (of any kind) to be used. It is implied that a LockManager uses its own custom LockTracker. 2. Add definitions for Range Locking (class Endpoint and GetRangeLock() function. cheng-chang, is this what you've had in mind (should the PR have both item 1 and item 2?) Pull Request resolved: https://github.com/facebook/rocksdb/pull/7443 Reviewed By: zhichao-cao Differential Revision: D24123172 Pulled By: cheng-chang fbshipit-source-id: c6548ad6d4cc3c25f68d13b29147bc6fdf357185
31 lines
847 B
C++
31 lines
847 B
C++
//
|
|
// Generic definitions for a Range-based Lock Manager
|
|
//
|
|
#pragma once
|
|
#ifndef ROCKSDB_LITE
|
|
|
|
#include "utilities/transactions/lock/lock_manager.h"
|
|
|
|
namespace ROCKSDB_NAMESPACE {
|
|
|
|
/*
|
|
A base class for all Range-based lock managers
|
|
|
|
See also class RangeLockManagerHandle in
|
|
include/rocksdb/utilities/transaction_db.h
|
|
*/
|
|
class RangeLockManagerBase : public LockManager {
|
|
public:
|
|
// Geting a point lock is reduced to getting a range lock on a single-point
|
|
// range
|
|
using LockManager::TryLock;
|
|
Status TryLock(PessimisticTransaction* txn, ColumnFamilyId column_family_id,
|
|
const std::string& key, Env* env, bool exclusive) override {
|
|
Endpoint endp(key.data(), key.size(), false);
|
|
return TryLock(txn, column_family_id, endp, endp, env, exclusive);
|
|
}
|
|
};
|
|
|
|
} // namespace ROCKSDB_NAMESPACE
|
|
#endif // ROCKSDB_LITE
|