commit | 9147f052c1713c5e5288d18555adfc624f20d45d | [log] [tgz] |
---|---|---|
author | Paul J. Davis <paul.joseph.davis@gmail.com> | Wed Sep 02 13:55:27 2020 -0500 |
committer | Paul J. Davis <paul.joseph.davis@gmail.com> | Wed Sep 02 14:05:12 2020 -0500 |
tree | 2a2fc733b15f2f3b830978882514ecffe28fdd76 | |
parent | 579e066c1402f41c7260631125f117b4dcdabf93 [diff] |
Add support for reporting conflicting keys Transactions that fail due to a conflict can be hard to debug. This exposes a recent feature that reports keys that were in conflict if a transaction has to be retried due to a conflict.
This project is a NIF wrapper for the FoundationDB C API. Documentation on the main API can be found here.
This project also provides a conforming implementation of the Tuple and Directory layers.
Assuming you have installed the FoundationDB C API library, building erlfdb is as simple as:
$ make
Alternatively, adding erlfdb as a rebar dependency should Just Work ®.
Documentation for installing FoundationDB can be found here for macOS or here for Linux.
A simple example showing how to open a database and read and write keys:
Eshell V9.3.3.6 (abort with ^G) 1> Db = erlfdb:open(<<"/usr/local/etc/foundationdb/fdb.cluster">>). {erlfdb_database,#Ref<0.2859661758.3941466120.85406>} 2> ok = erlfdb:set(Db, <<"foo">>, <<"bar">>). ok 3> erlfdb:get(Db, <<"foo">>). <<"bar">> 4> erlfdb:get(Db, <<"bar">>). not_found
FoundationDB has a custom binding tester that can be used to test whether changes have broken compatibility. See the BINDING_TESTER documentation for instructions on building and running that system.