Author: chetanm
Date: Mon Apr 13 08:43:50 2015
New Revision: 1673136
URL: http://svn.apache.org/r1673136
Log:
OAK-301- Document Oak
Add note about potential issue when using large MVP
Modified:
jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md
Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md
URL:
http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md?rev=1673136&r1=1673135&r2=1673136&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/dos_and_donts.md Mon Apr 13
08:43:50 2015
@@ -57,4 +57,11 @@ Oak scales to large number of direct chi
are *not* orderable. For orderable child nodes Oak keeps the order in an
internal property, which will lead to a performance degradation when the list
grows too large. For such scenarios Oak provides the ``oak:Unstructured`` node
-type, which is equivalent to ``nt:unstructured`` except that it is not
orderable.
\ No newline at end of file
+type, which is equivalent to ``nt:unstructured`` except that it is not
orderable.
+
+### Large Multi Value Property
+
+Using nodes with large multi value property would not scale well. Depending on
+NodeStore it might hit some size limit restriction also. For e.g. with
+DocumentMK the MVP would be stored in the backing Document which on Mongo has
a
+16MB limit.
