From fcebf6f72d7d5537440b561c8ff0fc71bb15a6f1 Mon Sep 17 00:00:00 2001 From: Glauber Costa Date: Thu, 15 Oct 2015 23:10:28 +0200 Subject: [PATCH] sstable tests: don't use set_generation method There is no reason aside from testing for a table to just change its generation number. There will be, however, when we support loading new sstables. The method however needs to be completely rewritten, so let's make sure the tests are not using that. Signed-off-by: Glauber Costa --- tests/sstable_test.cc | 2 +- tests/sstable_test.hh | 4 ++++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/tests/sstable_test.cc b/tests/sstable_test.cc index 6e3a536526..fadc4c2eba 100644 --- a/tests/sstable_test.cc +++ b/tests/sstable_test.cc @@ -172,7 +172,7 @@ SEASTAR_TEST_CASE(big_summary_query_32) { static future do_write_sst(sstring dir, unsigned long generation) { auto sst = make_lw_shared("ks", "cf", dir, generation, la, big); return sst->load().then([sst, generation] { - sst->set_generation(generation + 1); + sstables::test(sst).change_generation_number(generation + 1); auto fut = sstables::test(sst).store(); return std::move(fut).then([sst = std::move(sst)] { return make_ready_future(std::move(sst)); diff --git a/tests/sstable_test.hh b/tests/sstable_test.hh index 16a66b749f..4b744977c9 100644 --- a/tests/sstable_test.hh +++ b/tests/sstable_test.hh @@ -96,6 +96,10 @@ public: return _sst->binary_search(entries, sk); } + void change_generation_number(int64_t generation) { + _sst->_generation = generation; + } + future<> store() { _sst->_components.erase(sstable::component_type::Index); _sst->_components.erase(sstable::component_type::Data);