jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Update of "IndexingConfiguration" by ardschrijvers
Date Mon, 10 Sep 2007 08:51:55 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by ardschrijvers:
http://wiki.apache.org/jackrabbit/IndexingConfiguration

------------------------------------------------------------------------------
  </configuration>
  }}}
  
- The configuration above means that the property "mytext" for the entire workspace is indexed
(ans searched) with the lucene KeywordAnalyzer, and property "mytext2" with WhitespaceAnalyzer.
Using different analyzers for different languages is specifically useful.
+ The configuration above means that the property "mytext" for the entire workspace is indexed
(and searched) with the lucene keywordAnalyzer, and property "mytext2" with whitespaceAnalyzer.
Using different analyzers for different languages is specifically useful.
  
  Though, when using analyzers, you may find unexpected behavior when searching within a property
compared to searching within a node scope: 
  When your query is for example:
@@ -217, +217 @@

  
  and the property "mytext" contained the text : "testing my analyzers". 
  
- Now, when not having configured any analyzers for the property "mytext", this xpath does
not return a hit in the node with the property above. Also xpath = "//*[jcr:contains(.,'analyzer')]",
won't give a hit. Realize, that you can only set specific analyzers on a node property, and
that the node scope indexing/analyzing always is done with the globally defined analyzer in
SearchIndex element. Now, when I would change the analyzer used to indexed the "mytext" property
above to 
+ Now, when not having configured any analyzers for the property "mytext" (and not changed
the default analyzer in SearchIndex), this xpath does not return a hit in the node with the
property above. Also xpath = "//*[jcr:contains(.,'analyzer')]", won't give a hit. Realize,
that you can only set specific analyzers on a node property, and that the node scope indexing/analyzing
always is done with the globally defined analyzer in SearchIndex element. Now, when I would
change the analyzer used to indexed the "mytext" property above to 
  
  {{{
  <analyzer class="org.apache.lucene.analysis.Analyzer.GermanAnalyzer">

Mime
View raw message