Apache
/
lucene
mirror of https://github.com/apache/lucene.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

LUCENE-8497: Fix reference to MultiTermAwareComponenent in Solr reference guide

This commit is contained in:
Alan Woodward 2018-11-19 12:12:24 +00:00
parent 65486442c4
commit c2bd3aed22
1 changed files with 8 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
solr/solr-ref-guide/src/analyzers.adoc
View File

@ -87,9 +87,15 @@ At query time, the only normalization that happens is to convert the query terms
=== Analysis for Multi-Term Expansion
In some types of queries (i.e., Prefix, Wildcard, Regex, etc.) the input provided by the user is not natural language intended for Analysis. Things like Synonyms or Stop word filtering do not work in a logical way in these types of Queries.
In some types of queries (i.e., Prefix, Wildcard, Regex, etc.) the input provided
by the user is not natural language intended for Analysis. Things like Synonyms
or Stop word filtering do not work in a logical way in these types of Queries.
The analysis factories that _can_ work in these types of queries (such as Lowercasing, or Normalizing Factories) are known as {lucene-javadocs}/analyzers-common/org/apache/lucene/analysis/util/MultiTermAwareComponent.html[`MultiTermAwareComponents`]. When Solr needs to perform analysis for a query that results in Multi-Term expansion, only the `MultiTermAwareComponents` used in the `query` analyzer are used, Factory that is not Multi-Term aware will be skipped.
When Solr needs to perform analysis for a query that results in multi-term
expansion, then the `normalize` method is called for each factory in the filter
chain. Factories that provide filters that do not make sense in this context
will return their inputs unchanged. Normalization applies to both CharFilters
and TokenFilters
For most use cases, this provides the best possible behavior, but if you wish for absolute control over the analysis performed on these types of queries, you may explicitly define a `multiterm` analyzer to use, such as in the following example: