Page History

...

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

Works the same as contains but uses the literal Property Value enabling searches on special characters. 

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

Literal

All special characters are taken literally.  Since we usually normalize we can search on a string with colons, parentheses and other special characters using this search. 

Weighted Double Metaphone Lucene Query

Search with the Lucene query syntax, using a 'sounds like' algorithm.  A search for 'atack' will get a hit on 'attack'  Also, the exact user-entered text is taken into account -- so correct spelling will override the 'sounds like' algorithm.  Searches on the same indexed property value as the other double metaphone search.  Does not add anything more to the index, but does add more overhead to the search.

Literal Substring

The same as the substring search but with special characters enabled.  However this doesn't seem to make use of the optimized reverse string. It may be slower as a result.

Double Metaphone Lucene Query

...