Go to file
Alec Grieser 23f86132f5
Resolves #1235: Java: FDBExceptions are created successful operation completion (#1236)
The native function `NativeFuture::Future_getError` now returns `null` when the error code is 0 instead of an `FDBException` with a "Success" message and an error code of 0. This was only used in two places within the codebase; those two places now check for `null` errors and treats them like successes.
2019-03-07 11:28:13 -08:00
FDBLibTLS suppressed a spammy trace event 2018-11-07 21:05:49 -08:00
bindings Resolves #1235: Java: FDBExceptions are created successful operation completion (#1236) 2019-03-07 11:28:13 -08:00
build Added support for variable build directory 2019-02-12 17:01:04 -08:00
design Backup design documentation. 2018-02-22 18:09:41 -08:00
documentation Resolves #1235: Java: FDBExceptions are created successful operation completion (#1236) 2019-03-07 11:28:13 -08:00
fdbbackup Bug fix, restore start dry run would not open a trace file. 2019-01-09 03:54:13 -08:00
fdbcli changing the database configuration now checks that enough processes exist to support the new configuration 2018-11-30 18:52:24 -08:00
fdbclient An HTTP RequestID/ResponseID mismatch is logged as only a warning if the response code is 5xx and the responseID is empty. 2019-03-05 16:51:52 -08:00
fdbmonitor Bug fix, kill_process() modifies the id <-> pid maps so to kill all ids one by one the loop iterator must be advanced before the kill. 2018-11-08 16:21:50 -08:00
fdbrpc Bug fix in AsyncFileReadAhead where a file size that is an integer multiple of the read chunk size will cause a crash when reading the file's final block. BackupContainerLocalDirectory now uses AsyncFileReadAhead in simulation to get simulation coverage of that class, and FileBackup will generate file sizes which expose the bug. 2019-02-28 00:22:38 -08:00
fdbserver Merge pull request #1019 from satherton/http-request-id 2019-01-09 13:29:37 -08:00
fdbservice Fix typo: orginal > original 2018-04-20 17:29:13 +09:00
flow Merge pull request #1019 from satherton/http-request-id 2019-01-09 13:29:37 -08:00
layers remove trailing whitespace from our copyright headers ; fixed formatting of python setup.py 2018-02-21 10:25:11 -08:00
packaging update installer WIX GUID following release 2019-01-09 15:32:00 -08:00
recipes bump API version from 520 to 600 2018-07-09 11:00:57 -07:00
tests Removing test spec for old test which no longer exists. 2018-11-13 03:10:03 -08:00
.clang-format Add a clang-format config file. 2018-03-29 12:10:12 -07:00
.gitignore Exclude .vs folder (Visual Studio 2017) 2018-05-12 15:20:52 +02:00
ACKNOWLEDGEMENTS Initial repository commit 2017-05-25 13:48:44 -07:00
CODE_OF_CONDUCT.md Updates markdown link to Contributor Covenant homepage in the Code of Conduct. 2018-04-18 01:08:55 -04:00
CONTRIBUTING.md Adds initial draft of contribution guide. 2018-04-12 17:59:32 -07:00
LICENSE Initial repository commit 2017-05-25 13:48:44 -07:00
Makefile Added fdb-c-tests target to bindings target 2018-09-17 13:41:55 -07:00
README.md Update Linux compilation instructions 2018-04-23 14:43:09 +01:00
foundationdb.sln removed references to nodejs bindings 2018-04-06 17:17:45 -07:00
versions.target update versions target to 6.0.19 2019-01-09 15:31:59 -08:00

README.md

FoundationDB logo

FoundationDB is a distributed database designed to handle large volumes of structured data across clusters of commodity servers. It organizes data as an ordered key-value store and employs ACID transactions for all operations. It is especially well-suited for read/write workloads but also has excellent performance for write-intensive workloads. Users interact with the database using API language binding.

To learn more about FoundationDB, visit foundationdb.org

Documentation

Documentation can be found online at https://apple.github.io/foundationdb/. The documentation covers details of API usage, background information on design philosophy, and extensive usage examples. Docs are built from the source in this repo.

Forums

The FoundationDB Forums are the home for most of the discussion and communication about the FoundationDB project. We welcome your participation! We want FoundationDB to be a great project to be a part of and, as part of that, have established a Code of Conduct to establish what constitutes permissible modes of interaction.

Contributing

Contributing to FoundationDB can be in contributions to the code base, sharing your experience and insights in the community on the Forums, or contributing to projects that make use of FoundationDB. Please see the contributing guide for more specifics.

Getting Started

Binary downloads

Developers interested in using the FoundationDB store for an application can get started easily by downloading and installing a binary package. Please see the downloads page for a list of available packages.

Compiling from source

Developers on a OS for which there is no binary package, or who would like to start hacking on the code can get started by compiling from source.

macOS

  1. Check out this repo on your Mac.
  2. Install the Xcode command-line tools.
  3. Download version 1.52 of Boost.
  4. Set the BOOSTDIR environment variable to the location containing this boost installation.
  5. Install Mono.
  6. Install a JDK. FoundationDB currently builds with Java 8.
  7. Navigate to the directory where you checked out the foundationdb repo.
  8. Run make.

Linux

  1. Install Docker.
  2. Check out the foundationdb repo.
  3. Build Linux docker image using the file Dockerfile located in the build source directory.
  4. Run the docker image interactively Docker Run with the directory containing the foundationdb repo mounted Docker Mounts. docker run -it -v '/local/dir/path/foundationdb:/docker/dir/path/foundationdb' /bin/bash
  5. Navigate to the mounted directory containing the foundationdb repo. cd /docker/dir/path/foundationdb
  6. Run make.

This will build the fdbserver binary and the python bindings. If you want to build our other bindings, you will need to install a runtime for the language whose binding you want to build. Each binding has an .mk file which provides specific targets for that binding.