You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-commits@jackrabbit.apache.org by mr...@apache.org on 2021/05/14 15:19:31 UTC

svn commit: r1889897 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md

Author: mreutegg
Date: Fri May 14 15:19:31 2021
New Revision: 1889897

URL: http://svn.apache.org/viewvc?rev=1889897&view=rev
Log:
OAK-301 - Document Oak

Add note about MongoDB document size limit

Modified:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md

Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md?rev=1889897&r1=1889896&r2=1889897&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences.md Fri May 14 15:19:31 2021
@@ -320,6 +320,19 @@ With the document storage backend (Mongo
 a limit of 150 UTF-8 bytes on the length of the node names.
 See also [OAK-2644](https://issues.apache.org/jira/browse/OAK-2644).
 
+MongoDB Document Limit
+----------------------
+
+MongoDB has a document size limit of 16 MB. When using the document storage
+backend on MongoDB, adding a node with large String properties may fail because
+their combined size hits this limit. Consider storing large String values as
+Binary instead. Oak will put those values in the BlobStore, and the document
+only contains a much smaller reference to the Binary value.
+
+This limitation can also be hit when a node has many orderable child nodes
+because Oak internally stores the sequence of child node names in a hidden
+property. See also [do's and don'ts](dos_and_donts.html).
+
 Session Attributes
 ------------------