Database Word Query Configuration Help

Use the Word Query configuration page to modify the way cts:word-query searches are resolved in this database. Use this configuration to specify elements to include or exclude in all word queries, to add extra index options to the word queries, to specify query weights that apply to specific elements for relevance calculations, and to constrain which elements are included by a specified attribute value.

The bold type on any index setting name indicates that the index setting is inherited from the database configuration.

The following are the configuration options:

• include document root specifies if word query should begin including elements at the root element for each document (unless that element is explicitly excluded). This is set to true by default, which means all content is included unless you explicitly exclude one or more elements. Word query cannot have field paths.

• field path is not allowed on word query field.

• stemmed searches specifies whether index terms should be included in the database files to support stemming. When set to basic, basic stemming is enabled, and the shortest stem of each word is indexed. When set to advanced, all stems of each word are indexed. When set to decompounding, all stems are indexed, and smaller component words of large compound words are also indexed. Each successive level of stemming improves recall of word searches, but also causes slower document loads and larger database files.
• word searches specifies whether index terms should be included in the database files to support fast word searches. When this parameter is true, word searches are faster, but document loading is slower and the database files are larger.
• field value searches specifies whether index data is included which speeds up the performance of field value queries that use the cts:field-value-query function. Turn this index off if you are not interested in field value queries and if you want to conserve disk space and decrease loading time.
• field value positions specifies whether index data is included which speeds up the performance of proximity queries that use the cts:field-value-query function. Turn this index off if you are not interested in proximity queries and if you want to conserve disk space and decrease loading time.

---



• fast phrase searches specifies whether index terms should be included in the database files to support fast phrase searches. When this parameter is true, phrase searches are faster, but document loading is slower and the database files are larger.
• fast case sensitive searches specifies whether index terms should be included in the database files to support fast case-sensitive searches. When this parameter is true, case-sensitive searches are faster, but document loading is slower and the database files are larger.
• fast diacritic sensitive searches specifies whether index terms should be included in the database files to support fast diacritic-sensitive searches. When this parameter is true, diacritic-sensitive searches are faster, but document loading is slower and the database files are larger.

---



• trailing wildcard searches specifies whether indexes should be created to enable wildcard searches where the search pattern contains one or more consecutive non-wildcard characters at the beginning of the word, with the wildcard at the end of the word (for example, abc*). When this parameter is true, character searches are faster, but document loading is slower and the database files are larger.
• trailing wildcard word positions specifies whether index data should be included in the database files to enable proximity searches (cts:near-query) within trailing wildcard queries. You must also enable trailing wildcard searches in order to perform trailing wildcard position searches. When this parameter is true, positional searches are possible within a trailing wildcard query, but document loading is slower and the database files are larger.
• three character searches specifies whether indexes should be created to enable wildcard searches where the search pattern contains three or more consecutive non-wildcard characters (for example, abc*). When combined with a codepoint word lexicon, speeds the performance of any wildcard search (including searches with fewer than three consecutive non-wildcard characters). MarkLogic recommends combining the three character search index with a codepoint collation word lexicon. When this parameter is true, character searches are faster, but document loading is slower and the database files are larger.
• three character word positions specifies whether index data should be included in the database files to enable proximity searches (cts:near-query) within wildcard queries. You must also enable three character searches in order to perform wildcard position searches. When this parameter is true, positional searches are possible within a wildcard query, but document loading is slower and the database files are larger.
• two character searches specifies whether indexes should be created to enable wildcard searches where the search pattern contains two consecutive non-wildcard character (for example, ab*). This index is not needed if you have three character searches and a word lexicon.
• one character searches specifies whether indexes should be created to enable wildcard searches where the search pattern contains a single non-wildcard character (for example, a*). This index is not needed if you have three character searches and a word lexicon.

---



• included elements are elements that should be indexed for word query (i.e. elements that will be searched when doing a cts:word-query).
• excluded elements are elements that should not be indexed for word query (i.e. elements that will not be searched when doing a cts:word-query).