umgeher/leveled
0
Fork 0
Code Issues Pull requests Releases Activity Actions

Unit tets of lookup over-size issue

Browse source 
A mistake meant resetting to lookup on a skipped key would cause issues
if the skipped key ocurred under a no_lookup slot after the ?SLOT_SIZE
had been reached.  This caused the slot to switch to lookup, but beyond
the maximum size
This commit is contained in:
martinsumner 2017-03-11 00:03:55 +00:00
parent 4e4f498f20
commit a07770a3df
1 changed files with 12 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

12
src/leveled_sst.erl
View file

@ -1334,6 +1334,18 @@ generate_indexkeys(Count, IndexList) ->
generate_indexkeys(Count - 1, IndexList ++ Changes). generate_indexkeys(Count - 1, IndexList ++ Changes).
form_slot_test() ->
% If a skip key happens, mustn't switch to loookup by accident as could be
% over the expected size
SkippingKV = {{o, "B1", "K9999", null}, {9999, tomb, 1234567, {}}},
Slot = [{{o, "B1", "K5", null}, {5, active, 99234567, {}}}],
R1 = form_slot([SkippingKV], [],
{true, 99999999},
no_lookup,
?SLOT_SIZE + 1,
Slot),
?assertMatch({[], [], {no_lookup, Slot}}, R1).
indexed_list_test() -> indexed_list_test() ->
io:format(user, "~nIndexed list timing test:~n", []), io:format(user, "~nIndexed list timing test:~n", []),
N = 150, N = 150,