ComplexPhraseQueryParser
QueryParser which permits complex phrase query syntax eg "(john jon jonathan~) peters*".
Properties
Set to true to allow leading wildcard characters.
Set to true if phrase queries will be automatically generated when the analyzer returns more than one term from whitespace delimited text. NOTE: this behavior may not be suitable for all languages.
Sets the default Resolution used for certain field when no Resolution is defined for this field.
Set to true to enable position increments in result query.
Set the minimum similarity for fuzzy queries. Default is 2f.
Set the prefix length for fuzzy queries. Default is 0.
The actual operator that parser uses to combine query terms
Sets the default slop for phrases. If zero, then exact phrase matches are required. Default value is zero.
Generated Token Manager.
Functions
Disable tracing.
Returns a String where the escape char has been removed, or kept only once if there was a double escape.
Enable tracing.
Generate ParseException.
Returns the date resolution that is used by RangeQueries for the given field. Returns null, if no default or field specific date resolution has been set for the given field.
Returns the first query if splitOnWhitespace=true or otherwise the entire produced query
Sets the date resolution used by RangeQueries for a specific field.
Sets the boolean operator of the QueryParser. In default mode (OR_OPERATOR) terms without any modifiers are considered optional: for example capital of Hungary is equal to capital OR of OR Hungary.
In AND_OPERATOR mode terms are considered to be in conjunction: the above-mentioned query is parsed as capital AND of AND Hungary
When inOrder is true, the search terms must exists in the documents as the same order as in query.
Whether query text should be split on whitespace prior to analysis. Default is {@value #DEFAULT_SPLIT_ON_WHITESPACE}.
Trace enabled.