|
9 | 9 | <chapter> |
10 | 10 | <title>Legacy Full Text Index</title> |
11 | 11 | <section> |
| 12 | + <title>Note</title> |
12 | 13 | <note> |
13 | | - <para> |
14 | | - <span class="glyphicon glyphicon-warning-sign"/> |
15 | | - <b>Important:</b> |
16 | | - <span class="glyphicon glyphicon-warning-sign"/> |
17 | | - <br/>The Legacy Full Text Index should not be used anymore. The functionaly |
| 14 | + <para> |
| 15 | + <span class="glyphicon glyphicon-warning-sign"/> |
| 16 | + <b>Important:</b> |
| 17 | + <span class="glyphicon glyphicon-warning-sign"/> |
| 18 | + <br/>The Legacy Full Text Index should not be used anymore. The functionaly |
18 | 19 | will be removed from eXist-db in a future release, because it causes instability |
19 | 20 | for the database. Please use the Lucene based fulltext index instead. |
20 | 21 | </para> |
21 | | - </note> |
22 | | - |
23 | | - <para>This index is used to query for a sequence of separate "words" or tokens in a longer |
| 22 | + </note> |
| 23 | + <para>This index is used to query for a sequence of separate "words" or tokens in a longer |
24 | 24 | stream of text. While building the index, the text is parsed into single tokens which |
25 | 25 | are then stored in the index.</para> |
26 | | - <important> |
27 | | - <para>Historically, eXist has been creating a default full text index on all text nodes |
| 26 | + <important> |
| 27 | + <para>Historically, eXist has been creating a default full text index on all text nodes |
28 | 28 | and attribute values. This is no longer the case! Creating default indexes on data |
29 | 29 | which you may never use is too expensive, in particular, since eXist is now |
30 | 30 | providing a wider range of different indexes which can be much better optimized than |
31 | 31 | the default index and will offer superior performance.</para> |
32 | | - </important> |
33 | | - <para>Anyway, as for the other index types, you can configure the full text index in the |
| 32 | + </important> |
| 33 | + <para>Anyway, as for the other index types, you can configure the full text index in the |
34 | 34 | collection configuration and we will try to keep the configuration of the new index |
35 | 35 | backwards compatible. We thus recommend to create a collection configuration file, |
36 | 36 | disable the default index-all behaviour and define some explicit full text indexes on |
37 | 37 | your documents. The details of this process will be described below.</para> |
38 | | - <para>The full text index is only used in combination with eXist's fulltext search |
| 38 | + <para>The full text index is only used in combination with eXist's fulltext search |
39 | 39 | extensions. In particular, you can use the following eXist-specific operators and |
40 | 40 | functions that apply a fulltext index:</para> |
41 | | - <itemizedlist> |
42 | | - <listitem> |
43 | | - <para>Operators: <command>&=</command> and <command>|=</command> |
44 | | - </para> |
45 | | - </listitem> |
46 | | - <listitem> |
47 | | - <para>Main Functions: <function>text:match-all()</function>, |
| 41 | + <itemizedlist> |
| 42 | + <listitem> |
| 43 | + <para>Operators: <command>&=</command> and <command>|=</command> |
| 44 | + </para> |
| 45 | + </listitem> |
| 46 | + <listitem> |
| 47 | + <para>Main Functions: <function>text:match-all()</function>, |
48 | 48 | <function>text:match-any()</function> and <function>near()</function> |
49 | | - </para> |
50 | | - </listitem> |
51 | | - </itemizedlist> |
52 | | - <note> |
53 | | - <para>It is important to note that, if you have disabled full text indexing for certain |
| 49 | + </para> |
| 50 | + </listitem> |
| 51 | + </itemizedlist> |
| 52 | + <note> |
| 53 | + <para>It is important to note that, if you have disabled full text indexing for certain |
54 | 54 | elements, these operators and functions will also be effectively disabled, and will |
55 | 55 | not return matches. As a result, eXist will not return results for queries that |
56 | 56 | normally would have results provided fulltext indexing was enabled. Note also that |
57 | 57 | this is in direct contrast to the operation of range indexing, which does fallback |
58 | 58 | to full searching of the document if no range index applies (see below).</para> |
59 | | - </note> |
| 59 | + </note> |
60 | 60 | </section> |
61 | 61 | <section id="ftidxconf"> |
62 | 62 | <title>Full text index configuration</title> |
|
0 commit comments