Indexing should be restarted if conditions are changed

[GoogleCodeExporter]

If any of the collection spec is changed, indexing should be restarted for
that collection if it is in progress. Example: I get the file path wrong,
and return to correct it. 

Original issue reported on code.google.com by charliej...@gmail.com on 3 Dec 2007 at 12:38

[GoogleCodeExporter]

Hmm - I'm not sure about this one. At one point we had a similar feature 
implemented
and we got rid of it because it was causing problems. It's not hard to manually 
stop
the indexing and then start it once the collection is in the state that you 
want. I
think that if we're trying to stabalise things for 1.0 it would be better to 
leave
this off the milestone and look at it after 1.0.

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

• Changed state: Clarify

[GoogleCodeExporter]

OK, well we still have a problem with incorrect indexing settings. Example:

1. Create a collection
2. Use a non-existent path
3. Start indexing manually (enters 'In progress' state)
4. Edit the collection and change the path
5. Collection is still 'in progress' - and Holding and Unholding doesn't seem to
restart it with the new settings, as you might expect.

Original comment by charliej...@gmail.com on 5 Dec 2007 at 10:47

[GoogleCodeExporter]

OK, there was a problem with the log message when a file doesn't exist that was
causing the problem you describe. I've committed a fix for that, but it's 
really a
separate thing from the substance of this issue. I'm taking this issue off the
milestone for now following our discussions in irc.

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

• Removed labels: Milestone-Release1.0

[GoogleCodeExporter]

Original comment by charliej...@gmail.com on 27 Aug 2009 at 1:18

• Added labels: Module-FlaxBasic