Mercurial > p > roundup > code
diff 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 |
line wrap: on
line diff
--- a/doc/upgrading.txt Sun Jan 30 21:34:53 2022 -0500 +++ b/doc/upgrading.txt Mon Feb 07 22:52:03 2022 -0500 @@ -119,15 +119,16 @@ title) or in a message (or file) attached to the issue. One thing to note is that native-fts searches do not ignore words -longer than 25 characters or less than 2 characters. Also SQLite does -not filter out common works (i.e. there is no stopword list). So words +longer than 50 characters or less than 2 characters. Also SQLite does +not filter out common words (i.e. there is no stopword list). So words like "and", "or", "then", "with" ... are included in the FTS5 search. You must explicitly enable this search mechanism by changing the -``indexer`` setting in ``config.ini`` to ``native-fts``. Native-fts is -never chosen by default like xapian or whoosh. This prevents the -existing native indexing from being discarded if ``indexer`` is not -set. +``indexer`` setting in ``config.ini`` to ``native-fts``. Native-fts +must be explicitly chosen. This is different from Xapian or Whoosh +indexers, which are chosen if they are installed in the Python +environment. This prevents the existing native indexing from being +discarded if ``indexer`` is not set. Next re-index your data with ``roundup-admin -i tracker_home reindex``. This can take a while depending on the size of the tracker.