If using the AnalyzingLookupFactory as your lookupImpl, however, you have the option of defining the field type rules to use for index and query time analysis. However, this minimal analysis is not required if you want more analysis to occur on terms. One option for such a field type is shown here: In any event, you very likely want a minimal amount of analysis on the field, so an additional option is to create a field type in your schema that only uses basic tokenizers or filters. You may want to use copyField rules to create a special 'suggest' field comprised of terms from other fields in documents. To be used as the basis for a suggestion, the field must be stored. If sourceLocation is empty (meaning any dictionary implementation other than FileDictionaryFactory), then terms from this field in the index will be used. fieldĪ field from the index to use as the basis of suggestion terms.
However, if a sourceLocation is used, the dictionary implementation will be FileDictionaryFactory. If not set, the default dictionary implementation is HighFrequencyDictionaryFactory. There are several possible implementations, described below in the section Dictionary Implementations. If not set, the default lookup is JaspellLookupFactory. There are several possible implementations, described below in the section Lookup Implementations. It is possible to have multiples of these in one solrconfig.xml file. You can refer to this name in the URL parameters and in the SearchHandler configuration. SearchComponent name Arbitrary name for the search component.
0 kommentar(er)
