Mercurial > p > roundup > code
comparison doc/upgrading.txt @ 7400:d364ef1d66c2
doc batch reindex in upgrading file.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Wed, 24 May 2023 15:05:09 -0400 |
| parents | bb7752f6e1cd |
| children | 116ea5ce06ab |
comparison
equal
deleted
inserted
replaced
| 7399:deb8e7e6d66d | 7400:d364ef1d66c2 |
|---|---|
| 446 | 446 |
| 447 If you don't have messages assigned to multiple issues you | 447 If you don't have messages assigned to multiple issues you |
| 448 will see no change. If you do have multi-linked messages | 448 will see no change. If you do have multi-linked messages |
| 449 this will hopefully result in better message->issue | 449 this will hopefully result in better message->issue |
| 450 matching. | 450 matching. |
| 451 | |
| 452 Incremental/batch full test reindexing with roundup-admin (info) | |
| 453 ---------------------------------------------------------------- | |
| 454 | |
| 455 The ``reindex`` command in ``roundup-admin`` can reindex | |
| 456 a range of items. For example:: | |
| 457 | |
| 458 roundup-admin -i ... reindex issues:1-1000 | |
| 459 | |
| 460 will reindex only the first 1000 issues. This is useful since | |
| 461 reindexing can take a while and slow down the tracker. By running | |
| 462 it in batches you can control when the reindex runs rather than having | |
| 463 to wait for it to complete all the reindexing. See the man page or | |
| 464 `administration guide`_ for details. | |
| 451 | 465 |
| 452 .. index:: Upgrading; 2.1.0 to 2.2.0 | 466 .. index:: Upgrading; 2.1.0 to 2.2.0 |
| 453 | 467 |
| 454 Migrating from 2.1.0 to 2.2.0 | 468 Migrating from 2.1.0 to 2.2.0 |
| 455 ============================= | 469 ============================= |