GerHobbelt
commented
1 year ago I have seen this failure myself quite often (Lucene.NET is... flaky in Qiqqa when used with large libraries) and one thing to try that MAY help is to nuke the entire Lucene full text search index.
You can find those files in your Qiqqa data directory, where it keeps all your libraries, including its PDFs, etc.
Every library has it's own Qiqqa.library database plus documents directory (where all the imported PDFs are kept) plus an index directory.
You're looking for that index directory. Contents of which will look something like this:
Note that this is a screenshot of a tiny test library's Lucene.NET index. Your filenames may be different, but the set of file extensions would be quite similar, while your file sizes would be much larger than these!
and the key to having Qiqqa restart / recreating the search index is to delete all the files in that index directory.
WARNING:
If you don't trust yourself with this, make sure to ask someone well versed in working with Windows;
you can delete ('nuke') the Lucene search index any time and Qiqqa won't like it and start to work in a background task to recreate it (this can take hours to days for large/very large libraries as all PDFs will be reprocessed.
what you MUST NEVER DO is delete the Qiqqa.library file in the parent directory as that's where all your important library metadata is kept, so best would be to take the time to make a full backup before attempting this.
Hi.
Using V82.0.7357.40407 I have a library of over 180k files (too big to work properly?). I believe the search function stopped working at some point after I started importing through watched folder, after which it started returning zero or the same outdated results.
I used the 'rebuild library search indices' configuration but to no avail.
Is there any way to reverse this, or is my library broken for good, requiring a backup and restore?