comparison doc/upgrading.txt @ 6613:2eec7a500333

Doc updates for indexers. change word size max from 25 to 50 phrase search syntax updated clear up wording for automatic selection of xapian/whoosh link user_guide to admin_guide for finding syntax for native_fts searches.
author John Rouillard <rouilj@ieee.org>
date Mon, 07 Feb 2022 22:52:03 -0500
parents 0d99ae7c8de6
children 120b0bb05b6e
comparison
equal deleted inserted replaced
6612:d05800c6bdfa 6613:2eec7a500333
117 (`native`). So the search string `fts search` will find all issues 117 (`native`). So the search string `fts search` will find all issues
118 that have both of those words (an AND search) in a text-field (like 118 that have both of those words (an AND search) in a text-field (like
119 title) or in a message (or file) attached to the issue. 119 title) or in a message (or file) attached to the issue.
120 120
121 One thing to note is that native-fts searches do not ignore words 121 One thing to note is that native-fts searches do not ignore words
122 longer than 25 characters or less than 2 characters. Also SQLite does 122 longer than 50 characters or less than 2 characters. Also SQLite does
123 not filter out common works (i.e. there is no stopword list). So words 123 not filter out common words (i.e. there is no stopword list). So words
124 like "and", "or", "then", "with" ... are included in the FTS5 search. 124 like "and", "or", "then", "with" ... are included in the FTS5 search.
125 125
126 You must explicitly enable this search mechanism by changing the 126 You must explicitly enable this search mechanism by changing the
127 ``indexer`` setting in ``config.ini`` to ``native-fts``. Native-fts is 127 ``indexer`` setting in ``config.ini`` to ``native-fts``. Native-fts
128 never chosen by default like xapian or whoosh. This prevents the 128 must be explicitly chosen. This is different from Xapian or Whoosh
129 existing native indexing from being discarded if ``indexer`` is not 129 indexers, which are chosen if they are installed in the Python
130 set. 130 environment. This prevents the existing native indexing from being
131 discarded if ``indexer`` is not set.
131 132
132 Next re-index your data with ``roundup-admin -i tracker_home 133 Next re-index your data with ``roundup-admin -i tracker_home
133 reindex``. This can take a while depending on the size of the tracker. 134 reindex``. This can take a while depending on the size of the tracker.
134 135
135 You may want to update your ``config.ini`` by following the directions 136 You may want to update your ``config.ini`` by following the directions

Roundup Issue Tracker: http://roundup-tracker.org/