mirrors/scylladb
1
0
Fork 0
mirror of https://github.com/scylladb/scylladb.git synced 2026-06-03 05:26:58 +00:00
Code Issues Packages Projects Releases Wiki Activity

sstable tests: don't use set_generation method

Browse Source 
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 <glommer@scylladb.com>
This commit is contained in:
Glauber Costa
2015-10-15 23:10:28 +02:00
parent f3bad2032d
commit fcebf6f72d
2 changed files with 5 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
tests/sstable_test.cc
View File

@@ -172,7 +172,7 @@ SEASTAR_TEST_CASE(big_summary_query_32) {
static future<sstable_ptr> do_write_sst(sstring dir, unsigned long generation) {
auto sst = make_lw_shared<sstable>("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<sstable_ptr>(std::move(sst));

4
tests/sstable_test.hh
View File

@@ -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);