Author: catholicon
Date: Fri Jan 22 22:21:07 2016
New Revision: 1726332
URL: http://svn.apache.org/viewvc?rev=1726332&view=rev
Log:
OAK-2477: Move suggester specific config to own configuration node
Update documentation
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=1726332&r1=1726331&r2=1726332&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 Fri Jan 22
22:21:07 2016
@@ -955,7 +955,11 @@ properties terms to be used for suggesti
Once the above configuration has been done, by default, the Lucene suggester
is
updated every 10 minutes but that can be changed by setting the property
-`suggestUpdateFrequencyMinutes` in the index definition node to a different
value.
+`suggestUpdateFrequencyMinutes` in `suggestion` node under the index definition
+node to a different value.
+_Note that up till Oak 1.3.14, `suggestUpdateFrequencyMinutes` was to be setup
at
+index definition node itself. That is is still supported for backward
compatibility,
+but having a separate `suggestion` node is preferred._
Sample configuration for suggestions based on terms contained in
`jcr:description`
property.
@@ -966,7 +970,8 @@ property.
- compatVersion = 2
- type = "lucene"
- async = "async"
- - suggestUpdateFrequencyMinutes = 60
+ + suggestion
+ - suggestUpdateFrequencyMinutes = 20
+ indexRules
- jcr:primaryType = "nt:unstructured"
+ nt:base
@@ -988,9 +993,12 @@ Analyzed suggestions can be enabled by s
- compatVersion = 2
- type = "lucene"
- async = "async"
- - suggestUpdateFrequencyMinutes = 60
- - suggestAnalyzed = true
+ + suggestion
+ - suggestUpdateFrequencyMinutes = 20
+ - suggestAnalyzed = true
```
+_Note that up till Oak 1.3.14, `suggestAnalyzed` was to be setup at index
definition node itself. That is is still
+supported for backward compatibility, but having a separate `suggestion` node
is preferred._
Setting up `useInSuggest=true` for a property definition having
`name=:nodeName` would add node names to
suggestion dictionary (See [property name](#property-names) for node name
indexing)
