![]() ![]() NonFuzzyPrefix: The length of the common non fuzzy prefix match which must match a suggestion. Transpositions: If true, the default, transpositions should be treated as a primitive edit operation. Ma圎dits: The maximum number of string edits allowed. This means that token filters which leave gaps (for example, when StopFilter matches a stopword) the position would be respected when building the suggester. PreservePositionIncrements: If true, the suggester will preserve position increments. The default is -1 which means there is no limit. This places an upper-bound on how many expansions will be added for a single suggestion. MaxGraphExpansions: When building the FST ("index-time"), we add each path through the tokenstream graph as an individual entry. When there are too many surface forms we discard the lowest weighted ones. MaxSurfaceFormsPerAnalyzedForm: Maximum number of surface forms to keep for a single analyzed form. This means that suggestions are sensitive to tokenization (e.g., baseball is different from base ball). PreserveSep: If true, the default, then a separator between tokens is preserved. It’s usually preferred to have this setting set to 'false' and build suggesters manually issuing requests with suggest.build=true.ĮxactMatchFirst: If true, the default, exact suggestions are returned first, even if they are prefixes or other strings in the FST have larger weights. Enabling this to true could lead to the core talking longer to load (or reload) as the suggester data structure needs to be built, which can sometimes take a long time. If this parameter is not specified, the suggester will check if the lookup data structure is present on disk and build it if not found. If true then the lookup data structure will be built when Solr starts or when the core is reloaded. Some lookup implementations may take a long time to build, specially with large indexes, in such cases, using buildOnCommit or buildOnOptimize, particularly with a high frequency of softCommits is not recommended, and it’s recommended instead to build the suggester at a lower frequency by manually issuing requests with suggest.build=true. Use buildOnCommit to rebuild the dictionary with every soft-commit, or buildOnOptimize to build the dictionary only when the index is optimized. If false, the default, then the lookup data will be built only when requested by URL parameter suggest.build=true. If true then the lookup data structure will be rebuilt after soft-commit. The location to store the dictionary file. If this value is empty then the main index will be used as a source of terms and weights. The path to the dictionary file if using the FileDictionaryFactory. 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. ![]() If not set, the default dictionary implementation is HighFrequencyDictionaryFactory unless a sourceLocation is used, in which case, the dictionary implementation will be FileDictionaryFactory 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. ![]() You can refer to this name in the URL parameters and in the SearchHandler configuration. ParameterĪ symbolic name for this suggester. In the following sections additional parameters are provided for each implementation. Below are the main parameters that can be used no matter what lookup or dictionary implementation is used. The choice of the lookup implementation ( lookupImpl, how terms are found in the suggestion dictionary) and the dictionary implementation ( dictionaryImpl, how terms are stored in the suggestion dictionary) will dictate some of the parameters required. The Suggester search component takes several configuration parameters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |