wbtiger
/
foundationdb
mirror of https://github.com/apple/foundationdb.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
871 Commits 34 Branches 304 Tags 265 MiB
C++ 67.6%
C 19.1%
Python 4.2%
Java 3.3%
Go 1.5%
Other 4.1%
Go to file
Stephen Atherton 0e7d538c94 Bug fix, in recursive blob folder listings the recent removal of common prefixes from the result stream caused the list marker to not be set correctly when a folder level requires multiple requests due to folder size. 2018-01-06 20:58:48 -08:00
bindings updated documentation to reflect startNetwork starting a thread 2017-12-15 15:59:51 -08:00
build Patch up the makefiles and remove references to the completable bindings 2017-12-13 11:07:19 -08:00
design tuple and versionstamp documentation updates 2017-10-24 17:53:16 -07:00
fdbbackup Bug fixes. Fdbbackup delete was broken. Blobstore backup container deletion would do too much listing before deletions began due to list operations queueing up ahead of and starving the delete operations. Created new knob and blob endpoint limit for concurrent list operations to fix this. Increased blob request timeout default because some requests were taking longer. Crash fixes in blobstore doRequest() which wasn't checking that response object is valid before using it in error conditions. Filesystem-like backup container class (covering blobstore and local dirs) now ignores unrecognized filenames for describe() and expire() operations. 2018-01-05 23:06:39 -08:00
fdbcli Better message is displayed to the user. 2017-11-09 13:55:19 -08:00
fdbclient Bug fixes. Fdbbackup delete was broken. Blobstore backup container deletion would do too much listing before deletions began due to list operations queueing up ahead of and starving the delete operations. Created new knob and blob endpoint limit for concurrent list operations to fix this. Increased blob request timeout default because some requests were taking longer. Crash fixes in blobstore doRequest() which wasn't checking that response object is valid before using it in error conditions. Filesystem-like backup container class (covering blobstore and local dirs) now ignores unrecognized filenames for describe() and expire() operations. 2018-01-05 23:06:39 -08:00
fdbmonitor Add some comments to watch setting in fdbmonitor. 2018-01-04 11:31:01 -08:00
fdbrpc Bug fix, in recursive blob folder listings the recent removal of common prefixes from the result stream caused the list marker to not be set correctly when a folder level requires multiple requests due to folder size. 2018-01-06 20:58:48 -08:00
fdbserver Added new test that combines atomic backup/restore. Added randomization to delays in AtomicRestore workload. 2018-01-05 14:43:21 -08:00
fdbservice Initial repository commit 2017-05-25 13:48:44 -07:00
flow Renamed all TaskBucket backup tasks to more appropriate names. Created the ability to make task aliases and used this to direct old task names to a task definition which will abort backups created before version 5.1. 2018-01-04 22:53:31 -08:00
layers Remove a few more outdated items 2017-09-01 09:15:59 -07:00
packaging Merge branch 'release-5.0' 2017-11-02 10:42:30 -07:00
recipes Update API_VERSION from 500 to 510 2017-10-11 13:49:38 -07:00
tests Added new test that combines atomic backup/restore. Added randomization to delays in AtomicRestore workload. 2018-01-05 14:43:21 -08:00
.gitignore Initial repository commit 2017-05-25 13:48:44 -07:00
ACKNOWLEDGEMENTS Initial repository commit 2017-05-25 13:48:44 -07:00
LICENSE Initial repository commit 2017-05-25 13:48:44 -07:00
Makefile Patch up the makefiles and remove references to the completable bindings 2017-12-13 11:07:19 -08:00
README.md Initial repository commit 2017-05-25 13:48:44 -07:00
foundationdb.sln Initial repository commit 2017-05-25 13:48:44 -07:00
versions.target Update versions.target 2017-11-02 10:29:34 -07:00

README.md

FoundationDB

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.