Allow for setting max_keys to wrap Acc
Acc in response is now of form {Reason, Acc} not just Acc so that the application can understand the reason for the results ending - and take appropriate action (e.g. restart again from the LastKey to return more results).
This commit is contained in:
parent
142e3a17bb
commit
aaccd09a98
3 changed files with 22 additions and 7 deletions
|
@ -461,10 +461,10 @@ get_nextbucket(NextBucket, NextKey, Tag, LedgerSnapshot, BKList, {C, L}) ->
|
|||
ExtractFun,
|
||||
null),
|
||||
case R of
|
||||
null ->
|
||||
{no_more_keys, null} ->
|
||||
leveled_log:log("B0008",[]),
|
||||
BKList;
|
||||
{{B, K}, V} ->
|
||||
{_, {{B, K}, V}} ->
|
||||
case leveled_codec:is_active({Tag, B, K, null}, V, Now) of
|
||||
true ->
|
||||
leveled_log:log("B0009",[B]),
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue