For original testing in isolation I used this:
https://github.com/martinsumner/leveled/blob/master/test/volume/single_node/src/basho_bench_driver_eleveleddb.erl
But I've focused on testing since within Riak using the standard
basho_bench/examples/riakc_pb.config test
Testing of secondary indexin
Yup I get it, I like the concept and the fun naming of inkers, pencillers
and clerks as well. Is there a basho bench configuration? This reminds me a
bit if fractal trees but with a focus on NoSQL operational semantics, how
else do you see this adding improvements? It seems index requests could be
Have a look in
https://github.com/martinsumner/leveled/blob/master/docs/FUTURE.md and the
"Riak Features Implemented"
I'm trying to avoid the need for Riak to Get n times for every request
(both a KV GET and a KV PUT), when really it only needs the body once, and
the n-1 times it doesn't need the
Cheers indeed!
You added HEAD requests so a full GET wouldn't always be required?
Did I read that right? *dives into code*
%% GET requests first follow the path of a HEAD request, and if an object is
%% found, then fetch the value from the Journal via the Inker.
... WHAT?
Very nice work, will be m
