Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
For very fine grained content with many nodes and only few properties per node it would be more efficient to bundle multiple nodes into a single MongoDB document. Mostly reading would benefit because there are less roundtrips to the backend. At the same time storage footprint would be lower because metadata overhead is per document.
Feature branch - https://github.com/chetanmeh/jackrabbit-oak/compare/trunk...chetanmeh:OAK-1312
Feature Docs - http://jackrabbit.apache.org/oak/docs/nodestore/document/node-bundling.html
Attachments
Attachments
Issue Links
- is blocked by
-
OAK-4592 Make DocumentNodeState immutable
- Closed
- is related to
-
OAK-5091 Support bundled documents in oak-mongo.js
- Open
-
OAK-5070 Journal diff not working for changes in bundled node
- Closed
-
OAK-5226 Incorrect memory calculation for bundled node states
- Closed
-
OAK-6462 Incorrect memory calculation for bundled node states
- Closed
-
OAK-4928 Use Mongo sub document structure with bundling feature
- Open
-
OAK-4975 Setup a default Bundling config
- Closed
-
OAK-5045 Support bundling of nodes present in version store
- Closed
-
OAK-5079 Diff would not work for bundled nodes when done without journal support
- Closed
- relates to
-
OAK-4471 More compact storage format for Documents
- Open
-
OAK-210 granularity of persisted data
- Resolved
-
OAK-4959 Review the security aspect of bundling configuration
- Open
-
OAK-4960 Review the support for wildcards in bundling pattern
- Open