fdb-document-layer
fdb-document-layer copied to clipboard
FoundationDB
A document data model on FoundationDB, implementing MongoDB® wire protocol
This PR resolves [#133](https://github.com/FoundationDB/fdb-document-layer/issues/133) Modified document layer to open the listening connection before reading from FoundationDB cluster.
This PR resolves an issue [#143](https://github.com/FoundationDB/fdb-document-layer/issues/143). Updated all the syntax to support the python3. All test cases were executed and passed successfully
This PR resolves [#156](https://github.com/FoundationDB/fdb-document-layer/issues/156) The query parsing and validating part are moved to the constructor of updateDocument. Added test cases to verify existing functionalities.
This PR resolves [#91](https://github.com/FoundationDB/fdb-document-layer/issues/91) Stripped debug symbols into separate file as fdbdoc.debug
Usually, each MongoDB request is done in a single transaction, except for large reads and updates. In those cases, it's interesting to know the number of transactions per request. In...
Document Layer allows `$elemMatch` to work against nonarray fields, whereas MongoDB allows only on array fields. Array operators semantics are quite confusing already. Although allowing `$elemMatch` on nonarray fields allows...
Although this is tested with unit tests, its not added to deterministic correctness, we could be missing corner cases.
Although this is tested with unit tests, its not added to deterministic correctness, we could be missing corner cases.
It's just syntactic sugar on top of FDB transactions. This makes code much better and more readable by making it clear if a transaction was ever used for updates. We...
`NonIsolatedPlan` is used for requests that can't guarantee atomic operations. For example, updates or queries can have predicates that can match too many documents to read within 5 seconds, consequently...
Metadata
Owner
Metadata
A document data model on FoundationDB, implementing MongoDB® wire protocol