Erlang LevelDB API
C++ Erlang Shell Makefile
Latest commit 54bc385 Sep 14, 2016 @matthewvon matthewvon committed on GitHub Merge pull request #218 from basho/nem-comment-multi-backend-compress…
…ion-settings

Make multi_backend compression settings commented
Permalink
Failed to load latest commit information.
c_src snappy as default if nothing in riak.conf, default riak.conf sets lz4 Sep 7, 2016
priv Make multi_backend compression settings commented Sep 13, 2016
src snappy as default if nothing in riak.conf, default riak.conf sets lz4 Sep 7, 2016
test
.gitignore Have leveldb build its tools. Then copy those tools to ../priv direct… Jan 5, 2016
.travis.yml R15B03 is not available yet. Dec 31, 2012
BASHO_RELEASES update BASHO_RELEASES Sep 7, 2016
Makefile unify REBAR variable usage Mar 26, 2014
README.md Added a note that using fold is preferred Jun 7, 2016
rebar Updated leveldb schema tests. New version of rebar to match other repos. Jan 7, 2014
rebar.config Add tags for sed that mark lines removed to prevent cuttlefish from u… Jul 15, 2016
rebar.config.script add support for OS X Mavericks Oct 23, 2013
tools.mk Update tools.mk to 0.5.3 Mar 13, 2014

README.md

eleveldb - Erlang bindings to LevelDB datastore

Build Status

This repository follows the Basho standard for branch management as of November 28, 2013. The standard is found here:

https://github.com/basho/riak/wiki/Basho-repository-management

In summary, the "develop" branch contains the most recently reviewed engineering work. The "master" branch contains the most recently released work, i.e. distributed as part of a Riak release.

Iterating Records

High-level Iterator Interface

The interface that most clients of eleveldb should use when iterating over a set of records stored in leveldb is fold, since this fits nicely with the Erlang way of doing things.

For those who need more control over the process of iterating over records, you can use direct iterator actions. Use them with great care.

Direct Iterator Actions

seek/next/prev

  • seek: Move iterator to a new position.

  • next: Move forward one position and return the value; do nothing else.

  • prev: Move backward one position and return the value; do nothing else.

prefetc/prefetch_stop

  • prefetch: Perform a next action and then start a parallel call for the subsequent next while Erlang processes the current next. The subsequent prefetch may return immediately with the value already retrieved.

  • prefetch_stop: Stop a sequence of prefetch calls. If there is a parallel prefetch pending, cancel it, since we are about to move the pointer.

Warning

Either use prefetch/prefetch_stop or next/prev. Do not intermix prefetch and next/prev. You must prefetch_stop after one or more prefetch operations before using any of the other operations (seek, next, prev).