Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 5967:9a980675105d
Add reindex info to upgrading.doc
Recommended if you are affected by indexer code fixes, required if you
use whoosh and are upgrading to python 3.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Fri, 01 Nov 2019 19:53:58 -0400 |
| parents | 5148e46dd314 |
| children | e5acd1843517 |
comparison
equal
deleted
inserted
replaced
| 5966:8e4c5db44fde | 5967:9a980675105d |
|---|---|
| 49 you do not need to export and import, but need to delete the | 49 you do not need to export and import, but need to delete the |
| 50 ``db/otks`` and ``db/sessions`` files when changing Python version. | 50 ``db/otks`` and ``db/sessions`` files when changing Python version. |
| 51 If using the ``postgresql`` backend, you do not need to export and | 51 If using the ``postgresql`` backend, you do not need to export and |
| 52 import and no other special database-related steps are needed. | 52 import and no other special database-related steps are needed. |
| 53 | 53 |
| 54 If you use the whoosh indexer, you will need to reindex. It looks like | |
| 55 a database created with Python 2 leads to Unicode decode errors when | |
| 56 accessed by Python 3. Reindexing can take a while (see details below | |
| 57 look for "reindexing"). | |
| 58 | |
| 54 Octal values in config.ini change from the Python 2 representation | 59 Octal values in config.ini change from the Python 2 representation |
| 55 with a leading ``0`` (``022``). They now use a leading ``0o`` | 60 with a leading ``0`` (``022``). They now use a leading ``0o`` |
| 56 (``0o22``). Note that the ``0o`` format is properly handled under | 61 (``0o22``). Note that the ``0o`` format is properly handled under |
| 57 python 2. You can use the ``newconfig.ini`` generated using ``python3 | 62 python 2. You can use the ``newconfig.ini`` generated using ``python3 |
| 58 roundup-admin -i ... updateconfig newconfig.ini`` if you want to go | 63 roundup-admin -i ... updateconfig newconfig.ini`` if you want to go |
| 123 If you have not modified your tracker's userauditor.py, you can just | 128 If you have not modified your tracker's userauditor.py, you can just |
| 124 copy the userauditor.py from the classic template into your tracker's | 129 copy the userauditor.py from the classic template into your tracker's |
| 125 detectors directory. Otherwise merge the changes from the template | 130 detectors directory. Otherwise merge the changes from the template |
| 126 userauditor.py. https://issues.roundup-tracker.org/issue2550921 may be | 131 userauditor.py. https://issues.roundup-tracker.org/issue2550921 may be |
| 127 helpful. | 132 helpful. |
| 133 | |
| 134 Consider reindexing if you use European languages | |
| 135 ------------------------------------------------- | |
| 136 | |
| 137 A couple of bugs dealing with incorrect indexing of European languages | |
| 138 (Russian and German were reported) have been fixed. Note reindexing | |
| 139 all your data may take a long time. See: | |
| 140 https://issues.roundup-tracker.org/issue1195739 and | |
| 141 https://issues.roundup-tracker.org/issue1344046 for a description of | |
| 142 the problem. If you determine that this a problem for your tracker, | |
| 143 you can use:: | |
| 144 | |
| 145 roundup-admin -i /path/to/tracker reindex | |
| 146 | |
| 147 to rewrite your full text indexes. The tracker used for reindex timing | |
| 148 had 140MB of file/message data and 2500 issues with a slow 5400RPM | |
| 149 SATA drive. Using native indexing with sqlite took about 45 | |
| 150 minutes. Using whoosh took about 2 hours. Using xapian took about 6 | |
| 151 hours. All examples were with Python 2. Anecdotal evidence shows | |
| 152 Python 3 is faster, but YMMV. | |
| 128 | 153 |
| 129 Migrating from 1.5.1 to 1.6.0 | 154 Migrating from 1.5.1 to 1.6.0 |
| 130 ============================= | 155 ============================= |
| 131 | 156 |
| 132 Update tracker config file | 157 Update tracker config file |