Deleting a collection while it is indexing doesn't stop the indexing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a collection A and start indexing
2. Delete collection A
3. Create a collection B and start indexing

What is the expected output? What do you see instead?

B is marked as 'Due' rather than 'In progress' - it seems we're waiting for
the deleted collection to stop.

Original issue reported on code.google.com by charliej...@gmail.com on 23 Nov 2007 at 4:55

[GoogleCodeExporter]

This is part and parcel of the database deletion stuff not deleting the 
underlying
database.  I have a partial fix already, so assigning to myself.

Original comment by boulton.rj@gmail.com on 23 Nov 2007 at 5:09

[GoogleCodeExporter]

Another wrinkle; if an index is created to use a folder that doesn't exist or is
wrong, and then manually started, then one tries to correct the incorrect folder
setting, the indexer appears to get stuck. 

In general it might be best to inform the user if a setting they have changed is
going to necessitate a restart of the indexer from the beginning.

Original comment by charliej...@gmail.com on 29 Nov 2007 at 10:26

[GoogleCodeExporter]

Bumping this up a bit as it's very easy to break the system by confusing the 
indexer.

Original comment by charliej...@gmail.com on 30 Nov 2007 at 4:08

• Added labels: Priority-Critical
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Independently of anything that Richard is doing it would be easy enough just to 
stop
the indexing prior to deleting a collection. This wouldn't deal with the more 
general
problem of deleting the database when the collection goes, but should sort the
immediate problem.

Original comment by paul.x.r...@googlemail.com on 1 Dec 2007 at 11:32

[GoogleCodeExporter]

OK, can we do this? Also look at the whole issue of restarting the indexing if 
any of
the collection details change?

Original comment by charliej...@gmail.com on 3 Dec 2007 at 11:50

[GoogleCodeExporter]

I'll look at stopping indexing as part of the deletion thing. Restarting on 
changes
is really a separate thing - please make a new issue for it.

Original comment by paul.x.r...@googlemail.com on 3 Dec 2007 at 12:28

[GoogleCodeExporter]

I've done something to solve the immediate problem. I'll mark this as fixed 
since we
have issue 85 for the deletion of the underlying database thing.

Original comment by paul.x.r...@googlemail.com on 3 Dec 2007 at 1:24

• Changed state: Fixed