home | career | drupal | java | mac | mysql | perl | scala | uml | unix  

Lucene example source code file (queryparsersyntax.xml)

This example Lucene source code file (queryparsersyntax.xml) is included in the DevDaily.com "Java Source Code Warehouse" project. The intent of this project is to help you "Learn Java by Example" TM.

Java - Lucene tags/keywords

and, apache, apache, for, for, lucene, lucene, not, or, searches, term, the, the, this

The Lucene queryparsersyntax.xml source code

<?xml version="1.0"?>
<document>
	<header>
        <title>
	Apache Lucene - Query Parser Syntax
		</title>
	</header>
    <properties>
        <author email="carlson@apache.org">Peter Carlson
    </properties>
    <body>
        <section id="Overview">
            <title>Overview
            <p>Although Lucene provides the ability to create your own
            queries through its API, it also provides a rich query
            language through the Query Parser, a lexer which
            interprets a string into a Lucene Query using JavaCC.
	    </p>

	    <p>Generally, the query parser syntax may change from
	    release to release.  This page describes the syntax as of
	    the current release.  If you are using a different
	    version of Lucene, please consult the copy of
	    <code>docs/queryparsersyntax.html that was distributed
	    with the version you are using.
	    </p>

            <p>
            Before choosing to use the provided Query Parser, please consider the following:
            <ol>
            <li>If you are programmatically generating a query string and then
            parsing it with the query parser then you should seriously consider building
            your queries directly with the query API.  In other words, the query
            parser is designed for human-entered text, not for program-generated
            text.</li>

            <li>Untokenized fields are best added directly to queries, and not
            through the query parser.  If a field's values are generated programmatically
            by the application, then so should query clauses for this field.
            An analyzer, which the query parser uses, is designed to convert human-entered
            text to terms.  Program-generated values, like dates, keywords, etc.,
            should be consistently program-generated.</li>

            <li>In a query form, fields which are general text should use the query
            parser.  All others, such as date ranges, keywords, etc. are better added
            directly through the query API.  A field with a limit set of values,
            that can be specified with a pull-down menu should not be added to a
            query string which is subsequently parsed, but rather added as a
            TermQuery clause.</li>
            </ol>
            </p>
        </section>

        <section id="Terms">
            <title>Terms
        <p>A query is broken up into terms and operators. There are two types of terms: Single Terms and Phrases.

<p>A Single Term is a single word such as "test" or "hello".

<p>A Phrase is a group of words surrounded by double quotes such as "hello dolly".

<p>Multiple terms can be combined together with Boolean operators to form a more complex query (see below).

<p>Note: The analyzer used to create the index will be used on the terms and phrases in the query string. So it is important to choose an analyzer that will not interfere with the terms used in the query string.</p> </section> <section id="Fields"> <title>Fields <p>Lucene supports fielded data. When performing a search you can either specify a field, or use the default field. The field names and default field is implementation specific.

<p>You can search any field by typing the field name followed by a colon ":" and then the term you are looking for.

<p>As an example, let's assume a Lucene index contains two fields, title and text and text is the default field. If you want to find the document entitled "The Right Way" which contains the text "don't go this way", you can enter: </p> <source>title:"The Right Way" AND text:go <p>or

<source>title:"Do it right" AND right <p>Since text is the default field, the field indicator is not required.

<p>Note: The field is only valid for the term that it directly precedes, so the query

<source>title:Do it right <p>Will only find "Do" in the title field. It will find "it" and "right" in the default field (in this case the text field).

</section> <section id="Term Modifiers"> <title>Term Modifiers <p>Lucene supports modifying query terms to provide a wide range of searching options.

<section id="Wildcard Searches"> <title>Wildcard Searches <p>Lucene supports single and multiple character wildcard searches within single terms (not within phrase queries).</p> <p>To perform a single character wildcard search use the "?" symbol.

<p>To perform a multiple character wildcard search use the "*" symbol.

<p>The single character wildcard search looks for terms that match that with the single character replaced. For example, to search for "text" or "test" you can use the search:

<source>te?t <p>Multiple character wildcard searches looks for 0 or more characters. For example, to search for test, tests or tester, you can use the search:

<source>test* <p>You can also use the wildcard searches in the middle of a term.

<source>te*t <p>Note: You cannot use a * or ? symbol as the first character of a search.

</section> <section id="Fuzzy Searches"> <title>Fuzzy Searches <p>Lucene supports fuzzy searches based on the Levenshtein Distance, or Edit Distance algorithm. To do a fuzzy search use the tilde, "~", symbol at the end of a Single word Term. For example to search for a term similar in spelling to "roam" use the fuzzy search:

<source>roam~ <p>This search will find terms like foam and roams.

<p>Starting with Lucene 1.9 an additional (optional) parameter can specify the required similarity. The value is between 0 and 1, with a value closer to 1 only terms with a higher similarity will be matched. For example:

<source>roam~0.8 <p>The default that is used if the parameter is not given is 0.5.

</section> <section id="Proximity Searches"> <title>Proximity Searches <p>Lucene supports finding words are a within a specific distance away. To do a proximity search use the tilde, "~", symbol at the end of a Phrase. For example to search for a "apache" and "jakarta" within 10 words of each other in a document use the search:

<source>"jakarta apache"~10 </section> <section id="Range Searches"> <title>Range Searches <p>Range Queries allow one to match documents whose field(s) values are between the lower and upper bound specified by the Range Query. Range Queries can be inclusive or exclusive of the upper and lower bounds. Sorting is done lexicographically.</p> <source>mod_date:[20020101 TO 20030101] <p>This will find documents whose mod_date fields have values between 20020101 and 20030101, inclusive. Note that Range Queries are not reserved for date fields. You could also use range queries with non-date fields:</p> <source>title:{Aida TO Carmen} <p>This will find all documents whose titles are between Aida and Carmen, but not including Aida and Carmen.

<p>Inclusive range queries are denoted by square brackets. Exclusive range queries are denoted by curly brackets.</p> </section> <section id="Boosting a Term"> <title>Boosting a Term <p>Lucene provides the relevance level of matching documents based on the terms found. To boost a term use the caret, "^", symbol with a boost factor (a number) at the end of the term you are searching. The higher the boost factor, the more relevant the term will be.

<p>Boosting allows you to control the relevance of a document by boosting its term. For example, if you are searching for

<source>jakarta apache <p>and you want the term "jakarta" to be more relevant boost it using the ^ symbol along with the boost factor next to the term. You would type:</p> <source>jakarta^4 apache <p>This will make documents with the term jakarta appear more relevant. You can also boost Phrase Terms as in the example:

<source>"jakarta apache"^4 "Apache Lucene" <p>By default, the boost factor is 1. Although the boost factor must be positive, it can be less than 1 (e.g. 0.2)

</section> </section> <section id="Boolean operators"> <title>Boolean Operators <p>Boolean operators allow terms to be combined through logic operators. Lucene supports AND, "+", OR, NOT and "-" as Boolean operators(Note: Boolean operators must be ALL CAPS).</p> <section id="OR"> <p>The OR operator is the default conjunction operator. This means that if there is no Boolean operator between two terms, the OR operator is used. The OR operator links two terms and finds a matching document if either of the terms exist in a document. This is equivalent to a union using sets. The symbol || can be used in place of the word OR.</p> <p>To search for documents that contain either "jakarta apache" or just "jakarta" use the query:

<source>"jakarta apache" jakarta <p>or

<source>"jakarta apache" OR jakarta </section> <section id="AND"> <title>AND <p>The AND operator matches documents where both terms exist anywhere in the text of a single document. This is equivalent to an intersection using sets. The symbol && can be used in place of the word AND.</p> <p>To search for documents that contain "jakarta apache" and "Apache Lucene" use the query:

<source>"jakarta apache" AND "Apache Lucene" </section> <section id="+"> <title>+ <p>The "+" or required operator requires that the term after the "+" symbol exist somewhere in a the field of a single document.

<p>To search for documents that must contain "jakarta" and may contain "lucene" use the query:

<source>+jakarta lucene </section> <section id="NOT"> <title>NOT <p>The NOT operator excludes documents that contain the term after NOT. This is equivalent to a difference using sets. The symbol ! can be used in place of the word NOT.</p> <p>To search for documents that contain "jakarta apache" but not "Apache Lucene" use the query:

<source>"jakarta apache" NOT "Apache Lucene" <p>Note: The NOT operator cannot be used with just one term. For example, the following search will return no results:

<source>NOT "jakarta apache" </section> <section id="-"> <title>- <p>The "-" or prohibit operator excludes documents that contain the term after the "-" symbol.

<p>To search for documents that contain "jakarta apache" but not "Apache Lucene" use the query:

<source>"jakarta apache" -"Apache Lucene" </section> </section> <section id="Grouping"> <title>Grouping <p>Lucene supports using parentheses to group clauses to form sub queries. This can be very useful if you want to control the boolean logic for a query.

<p>To search for either "jakarta" or "apache" and "website" use the query:

<source>(jakarta OR apache) AND website <p>This eliminates any confusion and makes sure you that website must exist and either term jakarta or apache may exist.

</section> <section id="Field Grouping"> <title>Field Grouping <p>Lucene supports using parentheses to group multiple clauses to a single field.

<p>To search for a title that contains both the word "return" and the phrase "pink panther" use the query:

<source>title:(+return +"pink panther") </section> <section id="Escaping Special Characters"> <title>Escaping Special Characters <p>Lucene supports escaping special characters that are part of the query syntax. The current list special characters are

<p>+ - && || ! ( ) { } [ ] ^ " ~ * ? : \

<p>To escape these character use the \ before the character. For example to search for (1+1):2 use the query:

<source>\(1\+1\)\:2 </section> </body> </document>

Other Lucene examples (source code examples)

Here is a short list of links related to this Lucene queryparsersyntax.xml source code file:



my book on functional programming

 

new blog posts

 

Copyright 1998-2019 Alvin Alexander, alvinalexander.com
All Rights Reserved.

A percentage of advertising revenue from
pages under the /java/jwarehouse URI on this website is
paid back to open source projects.