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 ch...@apache.org on 2014/11/04 15:30:35 UTC
svn commit: r1636584 -
/jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md
Author: chetanm
Date: Tue Nov 4 14:30:34 2014
New Revision: 1636584
URL: http://svn.apache.org/r1636584
Log:
OAK-301 : oak docu
Remove recommendation for CopyOnRead for now
Modified:
jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md
Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md?rev=1636584&r1=1636583&r2=1636584&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/query/lucene.md Tue Nov 4 14:30:34 2014
@@ -370,24 +370,19 @@ index content e.g. size of index, number
Following are some best practices to get good performance from Lucene based
indexes
-1. Make use of [CopyOnRead](#copy-on-read) so as to enable local copying of
- Lucene index. This would enable use of memory mapped io on supported
- platforms and hence better performance/
-
-2. Make use on [non root indexes](#non-root-index). If you query always
+1. Make use on [non root indexes](#non-root-index). If you query always
perform search under certain paths then create index definition under those
paths only. This might be helpful in multi tenant deployment where each tenant
data is stored under specific repository path and all queries are made under
those path.
-3. Index only required data. Depending on your requirement you can create
+2. Index only required data. Depending on your requirement you can create
multiple Lucene indexes. For example if in majority of cases you are
querying on various properties specified under `<node>/jcr:content/metadata`
where node belong to certain specific nodeType then create single index
definition listing all such properties and restrict it that nodeType. You
can the size of index via mbean
-
[1]: http://www.day.com/specs/jsr170/javadocs/jcr-2.0/constant-values.html#javax.jcr.PropertyType.TYPENAME_STRING
[OAK-2201]: https://issues.apache.org/jira/browse/OAK-2201
[OAK-1724]: https://issues.apache.org/jira/browse/OAK-1724