Lucene in Action

...If a term contains an asterisk or a question mark, it's considered a Wildcard- Query. When the term only contains a trailing asterisk, QueryParser optimizes it to a PrefixQuery instead. Both prefix and wildcard queries are lowercased by default, but this behavior can be controlled: public void ... construct your own instance of QueryParser rather than use the static parse method. Wildcards ... leading wildcards (at the expense of per- formance). Section 3.4.6 discusses more about the performance... [Full sample chapter]

...Wildcard queries let you query for terms with missing pieces but still find matches. Two standard wildcard characters are used: * for zero or more characters, and ? for zero or one character. Listing ... the wildcard pattern is created as a Term (the pattern to match) even though it isn't explicitly used ... wildcard character) decreases the terms enumerated to find matches. Beginning a pattern with a wild- card query forces the term enumeration to search all terms in the index for matches. Oddly... [Full sample chapter]

... and wildcard queries by taking advantage of the Parse- Exception option. Listing 6.5 Disallowing wildcard and fuzzy queries public class CustomQueryParser extends QueryParser { public ... getWildcardQuery( String field, String termStr) throws ParseException { throw new ParseException("Wildcard ... users from executing wildcard and fuzzy queries, construct an instance of CustomQueryParser and use ... ("Wildcard queries should not be allowed"); } catch (ParseException expected) { // expected assertTrue...

... of text. Support for single and multiterm queries, phrase queries, wildcards, result ranking... [Full sample chapter]

... dis- ables the useful, yet expensive, wildcard and fuzzy queries. The last thing we want is for someone ... (String field, String term) throws ParseException { throw new ParseException("Wildcard Query not allowed...

...In section 3.5, we introduced QueryParser and showed that it has a few settings to control its behavior, such as setting the locale for date parsing and controlling the default phrase slop. QueryParser is also extensible, allowing subclassing to override parts of the query-creation process. In this section, we demonstrate sub- classing QueryParser to disallow inefficient wildcard and fuzzy queries, custom date-range handling, and morphing phrase queries into SpanNearQuerys instead...

...Lucene is fast and scalable. But how fast is it? Is it fast enough? Can you guaran- tee that searches are returned within a reasonable amount of time? How does Lucene respond under load? If your project has high performance demands, you've done the right thing by choosing Lucene, but don't let performance numbers be a mystery. There are sev- eral ways Lucene's performance can be negatively impacted by how you use it-- like using fuzzy or wildcard queries or a range query, as you'll see...

... 4.3.2 on StandardAnalyzer). A common question is why the asterisk isn't interpreted as a wildcard query... [Full sample chapter]

..., and other special expression syntax to denote range, wildcard, and fuzzy searches. QueryParser analyzes all...

... such as wildcard and fuzzy queries. Custom filters allow infor- mation from outside the index to factor...

... ranges by padding to match how numbers were indexed getWildcardQuery(String field, Wildcard queries can...

... to OR). These settings also include locale (for date parsing), default phrase slop, and whether to lowercase wildcard... [Full sample chapter]

... be rewritten in its most primitive form for Query- Scorer to be happy. For example, wildcard, fuzzy...

... that exact matches come first) and a wildcard query match- ing words with one or two more...

... distance 195 Keyword fields 122 affected by HitCollector 203 by index order 153 lowercasing wildcard...