Even when a crawl 'ends' -- URIs exhausted, limits
exceeded, etc. -- an operator might still want to
perform operations, such as readding certain
URIs/seeds, that can only be done to a 'live' crawl.
So, there should be an option to leave a crawl 'open'
even when ostensibly 'finished'.
This could be an option to be turned on/off, and if
there are no other jobs pending, it could always be done.
Karl Thiessen
Usability/UI
1.6.0
Public
|
Date: 2007-03-14 01:36
|
|
Date: 2005-08-11 22:05 Logged In: YES |
|
Date: 2004-12-15 18:25 Logged In: YES |
|
Date: 2004-11-19 18:42 Logged In: NO |
| Field | Old Value | Date | By |
|---|---|---|---|
| summary | hold paused crawl at \'end\', allowing all in-progress ops | 2006-09-11 22:32 | karl-ia |
| summary | hold paused crawl at 'end', allowing all in-progress ops | 2006-09-11 22:31 | karl-ia |
| close_date | - | 2005-12-02 17:29 | stack-sf |
| status_id | Open | 2005-12-02 17:29 | stack-sf |
| artifact_group_id | None | 2005-09-23 20:53 | gojomo |
| priority | 6 | 2005-09-23 18:37 | gojomo |
| assigned_to | gojomo | 2005-08-11 22:05 | gojomo |
| priority | 9 | 2004-12-15 18:25 | gojomo |
| priority | 7 | 2004-12-03 22:50 | gojomo |
| assigned_to | nobody | 2004-12-03 01:02 | gojomo |
| summary | hold crawl at 'end', allowing all in-progress ops | 2004-12-03 01:02 | gojomo |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use