Jump to navigation Jump to search
5,574 bytes added ,  11:35, 6 December 2010
Created page with "==Fuzzy Querying== In addition to the W3C XQFT Recommendation, BaseX supports fuzzy querying. The XQFT grammar was enhanced by the FTMatchOption <code>using fuzzy </code> to al..."
==Fuzzy Querying==
In addition to the W3C XQFT Recommendation, BaseX supports fuzzy querying.
The XQFT grammar was enhanced by the FTMatchOption <code>using fuzzy </code>
to allow for approximate searches in full texts.
By default, the standard full-text index already supports the efficient
execution of fuzzy searches.
<p><b>Document 'doc.xml'</b>:</p>
&lt;a&gt;foo bar&lt;/a&gt;
&lt;a&gt;foa bar&lt;/a&gt;
&lt;a&gt;faa bar&lt;/a&gt;
<p><b>Command:</b> <code>create db doc.xml; create index fullext</code>
<p><b>Query:</b> <code>xquery //a[text() contains text 'foo' using fuzzy]</code>
<p><b>Result:</b> <code>&lt;a&gt;foo bar&lt;/a&gt; &lt;a&gt;foa bar&lt;/a&gt;</code>

Fuzzy search is based on the Levenshtein distance. The maximum number of allowed
errors is calculated by dividing the token length of a specified query term by 4,
preserving a minimum of 1 errors. A static error distance can be set by adjusting
the <code>LSERR</code> property (default: <code>SET LSERR 0</code>).
The query above yields two results as there is no error between the query term
&quot;foo&quot; and the text node &quot;foo bar&quot;, and one error between
&quot;foo&quot; and &quot;foa bar&quot;.<br/>

==Query Evaluation==
BaseX offers different evaluation strategies for XQFT queries, the choice of which
depends on the input data and the existence of a full text index. The query compiler tries
to optimize and speed up queries by applying a full text index structure whenever
possible and useful. Three evaluation strategies are available: the standard sequential
database scan, a full-text index based evaluation and a hybrid one, combining both strategies
(see our <a target='_top' href='publications'>publications</a> for details).<br/><br/>
Query optimization and selection of the most efficient evaluation strategy is done
in a full-fledged automatic manner. The output of the query optimizer indicates which
evaluation plan is chosen for a specific query. It can be inspected by activating verbose
querying (Command: <code>SET VERBOSE ON</code>) or opening the Query Info in the GUI.
The message

<pre> Applying full-text index</pre>

suggests that the full-text index is applied to speed up query evaluation.
A second message

<pre> Removing path with no index results</pre>

indicates that the index does not yield any results for the specified term and
is thus skipped. If index optimizations are missing, it sometimes helps to give
the compiler a second chance and try different rewritings of the same query.<br/>

<p>To support a wide variety of scenarios, the available full-text index can
handle different combinations of the match options in XQuery Full Text.
By default, most indexing options are disabled. The GUI dialog for creating new databases
allows to choose the available options. On the command-line, the <code>SET</code>
command has to be used before the full-text index is created, either by</p>
<code> create index fulltext </code> or
<code> set ftindex on; create db FILENAME.xml</code>.

<p>The following options are available:</p>
<li>Support Wildcards: a trie-based index can be applied to support wildcard searches (<code>SET WILDCARDS ON</code>)</li>
<li>Stemming: tokens are stemmed with the Porter Stemmer before being indexed (<code>SET STEMMING ON</code>)</li>
<li>Case Sensitive: tokens are indexed in case-sensitive mode (<code>SET CASESEND ON</code>)</li>
<li>Diacritics: diacritics are indexed as well (<code>SET DIACRITICS ON</code>)</li>
<li>TF/IDF Scoring: TF/IDF-based scoring values are calculated and stored in the index (<code>SET SCORING 1/2</code>; details see below)</li>
<li> Stopwords: a stop word list can be defined to reduce the number of indexed tokens (<code>SET STOPWORDS FILENAME</code>)</li>

<p><b>Caution:</b> The index will only be applied if the activated options
are also specified in the query:</p>

<p><b>Index Options:</b> Case Sensitive, Stemming ON</p>
<p><b>Query 1 (wrong):</b>
//*[text() contains text 'inform']
<p><b>Query 2 (correct):</b>
//*[text() contains text 'inform' using case sensitive using stemming]
<p><b>Query 3 (correct):</b>
declare ft-option using case sensitive using stemming;
//*[text() contains text 'inform']

<p>The XQuery Full Text Recommendation allows for the usage of scoring models
and values within queries, with scoring being completely implementation defined.
BaseX offers an efficient internal scoring model which can be easily extended to
different application scenarios. Additionally, BaseX allows to store scoring
values within the full-text index structure. Three scoring types are currently
available, which can be adjusted with the <code>SCORING</code> property
(Default: <code>SET SCORING 0</code>):</p>
<li><code>0:</code> A standard algorithm is applied, which
considers the length of a term and its frequency in a single text node.
This algorithm is always applied if no index exists, or if the index cannot be
applied in a query.</li>
<li><code>1:</code> Standard TF/IDF algorithm, which treats document nodes
as document units</li>
<li><code>2:</code> Each text node is treated as a document unit in the
TF/IDF algorithm. This variant is recommendable for large XML files which
only contain one document node</li>

Anonymous user

Navigation menu