mirror of https://github.com/facebook/rocksdb.git
99daea3481
Summary: I'm anticipating using the public name HyperClockCache for both the current version with a fixed-size table and the upcoming version with an automatically growing table. However, for simplicity of testing them as substantially distinct implementations, I want to give them distinct internal names, like FixedHyperClockCache and AutoHyperClockCache. This change anticipates that by renaming to FixedHyperClockCache and assuming for now that all the unit tests run on HCC will run and behave similarly for the automatic HCC. Obviously updates will need to be made, but I'm trying to avoid uninteresting find & replace updates in what will be a large and engineering-heavy PR for AutoHCC Pull Request resolved: https://github.com/facebook/rocksdb/pull/11676 Test Plan: no behavior change intended, except logging will now use the name FixedHyperClockCache Reviewed By: ajkr Differential Revision: D48103165 Pulled By: pdillinger fbshipit-source-id: a33f1901488fea102164c2318e2f2b156aaba736 |
||
|---|---|---|
| .. | ||
| mock_time_env.cc | ||
| mock_time_env.h | ||
| secondary_cache_test_util.cc | ||
| secondary_cache_test_util.h | ||
| sync_point.cc | ||
| sync_point.h | ||
| sync_point_impl.cc | ||
| sync_point_impl.h | ||
| testharness.cc | ||
| testharness.h | ||
| testutil.cc | ||
| testutil.h | ||
| testutil_test.cc | ||
| transaction_test_util.cc | ||
| transaction_test_util.h | ||