Fiddle with naming in query API
Was easier in the calling applictaion to switch between using and not using a list of the Query format was consistent between those two cases.
This commit is contained in:
parent
c6b3fe78f4
commit
4bf6d3e73d
2 changed files with 20 additions and 19 deletions
|
@ -927,22 +927,9 @@ get_runner(State,
|
|||
SnapFun = return_snapfun(State, store, undefined, true, SnapPreFold),
|
||||
leveled_runner:foldobjects_allkeys(SnapFun, Tag, FoldFun, sqn_order);
|
||||
get_runner(State,
|
||||
{foldheads_bybucket,
|
||||
Tag, Bucket, KeyRange,
|
||||
FoldFun,
|
||||
JournalCheck, SnapPreFold, SegmentList}) ->
|
||||
{StartKey, EndKey, SnapQ} = return_ledger_keyrange(Tag, Bucket, KeyRange),
|
||||
SnapType = snaptype_by_presence(JournalCheck),
|
||||
SnapFun = return_snapfun(State, SnapType, SnapQ, true, SnapPreFold),
|
||||
leveled_runner:foldheads_bybucket(SnapFun,
|
||||
Tag,
|
||||
[{StartKey, EndKey}],
|
||||
FoldFun,
|
||||
JournalCheck, SegmentList);
|
||||
get_runner(State,
|
||||
{foldheads_bybucketlist,
|
||||
{foldheads_bybucket,
|
||||
Tag,
|
||||
BucketList,
|
||||
BucketList, bucket_list,
|
||||
FoldFun,
|
||||
JournalCheck, SnapPreFold, SegmentList}) ->
|
||||
KeyRangeFun =
|
||||
|
@ -957,6 +944,20 @@ get_runner(State,
|
|||
lists:map(KeyRangeFun, BucketList),
|
||||
FoldFun,
|
||||
JournalCheck, SegmentList);
|
||||
get_runner(State,
|
||||
{foldheads_bybucket,
|
||||
Tag,
|
||||
Bucket, KeyRange,
|
||||
FoldFun,
|
||||
JournalCheck, SnapPreFold, SegmentList}) ->
|
||||
{StartKey, EndKey, SnapQ} = return_ledger_keyrange(Tag, Bucket, KeyRange),
|
||||
SnapType = snaptype_by_presence(JournalCheck),
|
||||
SnapFun = return_snapfun(State, SnapType, SnapQ, true, SnapPreFold),
|
||||
leveled_runner:foldheads_bybucket(SnapFun,
|
||||
Tag,
|
||||
[{StartKey, EndKey}],
|
||||
FoldFun,
|
||||
JournalCheck, SegmentList);
|
||||
get_runner(State,
|
||||
{foldobjects_bybucket,
|
||||
Tag, Bucket, KeyRange,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue