Text Indexing and Lookup - eXist: A NoSQL Database and Application Development Platform - page 287

Figure 12-1. Example output for a search on “distinguish”
The full-text index definition is a child of the index element and, as is true of every‐
thing in a collection.xconf file, it is in the http://exist-db.org/collection-
config/1.0 namespace. It has the following structure:
<lucene>
analyzer*
text+
( inline | ignore )*
</lucene>
• The optional analyzer element allows you to change the analyzer class(es)
Lucene uses to analyze the text and/or pass it parameters. This is an advanced
topic, explained in “Defining and Configuring the Lucene Analyzer” on page 298 .
• The text element defines which elements/attributes Lucene creates an index for.
See more about this in “Choosing the correct context” on page 288 .
• The inline and ignore elements are important when you're indexing mixed
content. They can be defined either globally (as a child of lucene ) or for a spe‐
cific text element. Read more about this in “Handling Mixed Content” on page
290 .
Configuring the Search Context
The lucene/text element defines the context for the full-text index. This is usually
an element, but could just as well be an attribute. It has the following structure:
<text qname = string | match = string
boost? = float
analyzer? = NCName >
( inline | ignore )*
</text>