Author: catholicon
Date: Mon Jul 4 13:22:26 2016
New Revision: 1751277
URL: http://svn.apache.org/viewvc?rev=1751277&view=rev
Log:
OAK-301: Clarify precendence between different ways of configuring analyzers
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=1751277&r1=1751276&r2=1751277&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 Mon Jul 4
13:22:26 2016
@@ -666,6 +666,9 @@ Points to note
query for `range` (due to lower case filter) and won't give the result (as
might be
expected). An easy work-around for this example could be to have lower case
mappings
i.e. just use `domain => range`.
+4. Precedence: Specifying analyzer class directly has precedence over analyzer
configuration
+ by composition. If you want to configure analyzers by composition then
analyzer class
+ MUST NOT not be specified.
<a name="codec"></a>
#### Codec
