Bug #170
Option for resuming indexing when the scheduler is used.
| Status: | Closed | Start: | 02/20/2009 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | Karl Heinz Marbaise | % Done: | 100% |
|
| Category: | - | |||
| Target version: | 0.5.1 Europa | |||
Description
According to my contribution in the forum I herby issue the according feature request.
Please provide an option which permits to resume an existing index when starting SupoSE with the schedule option.
It would be impractible to merge the index of a finished indexing task of the currently running schedule process with the index which has been created before the schedule process has been interrupted every time when the indexing task of the currently running schedule process has finished.
User who make use of the tool cannot start a whole new index file every time they had to interrupt the schedule process when they also dont want the solution above (which is, as stated already, impractible).
Possible way of solution (steps):
1. Make SupoSE scan the existing index file and save the highest revision number found.
2. If 'fromrev' of config.ini is <= highest revision number of index then resume at this revision (highest revision found in index).
3. Else resume at 'fromrev' of config.ini
Weakness of this solution:
If the index has "wholes" (e.g. it a result of several merged indexes where revisions in between have been skipped) these wholes wont be covered.
I hope you will understand that users may really need a solution for that.
Thanks in advance.
Kind regards,
Mark Schlieker
History
Updated by Mark Schlieker 1079 days ago
Another way which doesnt require to scan the existing index file would be that there is an ini file in the folder where the index is created (or on the same level of the folder) where SupoSE writes the last revision it has incorporated into the index.
Updated by kama - 1078 days ago
- Status changed from New to Closed
- % Done changed from 0 to 100
Applied in changeset r231.
Updated by Karl Heinz Marbaise 1078 days ago
- Assigned to set to Karl Heinz Marbaise
- Target version changed from 0.5.0.1 Ceres to 0.5.1 Europa
Updated by Karl Heinz Marbaise 1078 days ago
Hi Mark,
Another way which doesnt require to scan the existing index file would be that there is an ini file in the folder where the index is created (or on the same level of the folder) where SupoSE writes the last revision it has incorporated into the index.
This is the approach which is implemented, but there has been a bug in it....
I hope Release 0.5.1 Europa will fix this.