Interrupted database indexing: must it always start over again?
Posted: 2021-07-14 15:51:48
I'm upgrading to 1.2.7 from 1.2.5, so I began the new indexing procedure. I have about 600,000 emails, and when the window showed 100,000+, I decided to close the window. In hindsight....
Closing the window seems to have interrupted the actual indexing. (I was going from the paradigm of an Apple System install, which always picks up where it left off if interrupted.) After failing to find the indexing window or a way a way to reopen it, I gave the rebuild database command, but the process appears to have started again from scratch. (Currently at 14K +) Was there a workaround that I missed?
If it always starts over after crash or interruption, is there a way to pause the indexing that doesn't crash the process and necessitate starting over? If not, consider this a feature suggestion! Thanks for info.
Kevin
Closing the window seems to have interrupted the actual indexing. (I was going from the paradigm of an Apple System install, which always picks up where it left off if interrupted.) After failing to find the indexing window or a way a way to reopen it, I gave the rebuild database command, but the process appears to have started again from scratch. (Currently at 14K +) Was there a workaround that I missed?
If it always starts over after crash or interruption, is there a way to pause the indexing that doesn't crash the process and necessitate starting over? If not, consider this a feature suggestion! Thanks for info.
Kevin