GitLab

kv_list_keys will give you all the keys in the database.  Still TODO:
implement the "starting key" feature, so we can get a subset of keys.

Split up "context" (the instance of the sds-keyval service) and
"database" (a specific collection of keys and values).

Furthermore, teach 'group' about this split.  Now a 'group' is a
collection of one context and one or more databases.

fixes #5 and #6
fully fixes #7

split up header into public and private/internal versions.

Fixes: #4

these small wrappers around margo init/finalize aren't helpful when
compositing with multiple services

David Rich authored Nov 17, 2017 and Rob Latham committed Nov 22, 2017

Build/test fixups. Note that there are 2 workarounds in place so test-mpi-group terminates cleanly: the ssg_finalize in the kv-server shutdown_handler and the commented out margo_finalize in the kvgroup_client_deregister function.

David Rich authored Nov 17, 2017 and Rob Latham committed Nov 22, 2017

First cut at adding distributed support. Implemented as separate client/server libs for now. Required some tweaking of the keyval API (see sds-keyval.h). May not compile yet.

David Rich authored Nov 01, 2017 and Rob Latham committed Nov 22, 2017

Simplify API. Handle arbitrary key/value types. Code still has explicit handling of bulk transfers. Unless this is a performance win, just let HG handle it all implicitly?

David Rich authored Oct 24, 2017 and Rob Latham committed Nov 22, 2017

Did a "spack install leveldb" to pull stock leveldb into sds-repo. Decoupled sds-keyval from ParSplice build environment.

David Rich authored Oct 10, 2017 and Rob Latham committed Nov 22, 2017

Bug in SDSKV client code caused puts for the same key to make it to the kv-server. Add a possible options framework for handling duplicates, etc.