This was intimated a while ago so I'm wondering if this ability has been put into 4.0c along with a fix for Merge Index?
bump!
4.0b contains code to detect common index corruption (and trigger a rebuild). Since we've only really been able to test it on indexes we have generated in house (we can't have you email us your 4GB index files...), we don't know exactly how many false negatives will be generated by the test. While we could have forced everyone to rebuild their indexes when they upgrade, we decided not to inflict this on everyone. The failure modes for a corrupt index are fairly well-known now, and it's relatively easy to force it to rebuild. (4.0b includes code to delete the existing index when "rebuild index" is entered, which eliminates many of the reasons to dig through %LOCALAPPDATA% to find the LibraryIndex files.)
(4.0b includes code to delete the existing index when "rebuild index" is entered, which eliminates many of the reasons to dig through %LOCALAPPDATA% to find the LibraryIndex files.)
[Y] This makes me very happy! Thanks for the info.
4.0b includes code to delete the existing index when "rebuild index" is entered, which eliminates many of the reasons to dig through %LOCALAPPDATA% to find the LibraryIndex files.
To clarify, Bradley:
Does "rebuild index" delete only the LibraryIndex? What is the situation for the Bible Index ie. does Rebuild Index affect both and perform the same deletion?
How do "Rebuild library index" and "rebuild bible index" work?
Thanks,
Does "rebuild index" delete only the LibraryIndex? What is the situation for the Bible Index ie. does Rebuild Index affect both and perform the same deletion? How do "Rebuild library index" and "rebuild bible index" work?
Good questions. "rebuild index" deletes both indexes. "rebuild library index" and "rebuild bible index" delete just the specified index (then rebuild it).
