 |
Page History
...
Search with the Lucene query syntax. http://lucene.apache.org/core/5_0_0/queryparser/org/apache/lucene/queryparser/classic/package-summary.html#package_description
Phrase
Searches for a Phrase in text using the regular lucene query parser. The only addition is a set of escaped quotation marks at the beginning and end of the phrase. It could be done in the regular Lucene Query by the user. No special indexing.
Contains
Equivalent to '* term* *' - in other words - a trailing wildcard on a term (but no leading wild card) and the term can appear at any position. Searches on Property Value only.
...
Exact match (case insensitive). Requires it's own indexed value, a lower case, untokenized Property Value.
SubString
Search based on a \"*some sub-string here*\". Functions much like the Java String.indexOf method. This requires two indexed fields to manage this without significant overhead. One field is the tokenized Property Value which causes no extra indexing, the other is reversed which requires an extra indexed field.
Spelling Error Tolerant Substring Match
Stemmed Lucene Query
Search with the Lucene query syntax, using stemmed terms. A search for 'trees' will get a hit on 'tree' This requires an extra indexed field when it is enabled in the load.
Literal Contains
Starts With
Equivalent to 'term*' (case insensitive) This runs against the same indexed Property Value as exactMatch so no extra indexing is needed. The query may require increased overhead however.
Non Leading Wild Card Literal Substring
...
A Regular Expression query. Searches against the lowercased text, so a regular expression that specifies an uppercase character will never return a match. Additionally, this searches against the entire string as a single token, rather than the tokenized string - so write your regular expression accordingly. This is the apache implementation of Regular Expression so follow their documentation as needed. This is from the old Jakarta project. We may want to update to the latest Lucene supported version of this. This runs against the same indexed value as exact match so it doesn't cost any more in terms of indexed data.
