I am running 4.5.1 on IIS7 and am trying to leverageExamine for search on a site with a ton of different content types. For now, I have this very basic search setup:
I get duplicates (triplicates, etc.) when I return results. This is fixed by publishing the page in question. When I then search again, I get only the one node back. The problem appears again if I 'Publish including children'. It appears the queue is not processed correctly with all the adds and deletes.
I get all the results in lower case; found this point from Slace (http://our.umbraco.org/forum/developers/extending-umbraco/11628-Lucene-Index-and-case) but it seems clunky to have to have this as a fix. Is there anything else that can be done to preserve the text casing for the results?
If you turn off async (runAsync="false" on the indexer) it'll log to the Umbraco log table when errors happen.
The only time I've see duplicate results if when the node exists multiple times in the Lucene store, and this happens when there's an error deleting.
As for lower-casing yes, there was a design decision made in Examine which forced lowercase of all content, RC3 (which dropped last week) does correct this by giving casing back to the Analyzer like it should. I'm almost finished a blog post explaining what to do.
Examine issues
Hi all,
I am running 4.5.1 on IIS7 and am trying to leverageExamine for search on a site with a ton of different content types. For now, I have this very basic search setup:
Here are a couple of things that I see happening:
Are you running Examine in async mode or not?
If you turn off async (runAsync="false" on the indexer) it'll log to the Umbraco log table when errors happen.
The only time I've see duplicate results if when the node exists multiple times in the Lucene store, and this happens when there's an error deleting.
As for lower-casing yes, there was a design decision made in Examine which forced lowercase of all content, RC3 (which dropped last week) does correct this by giving casing back to the Analyzer like it should. I'm almost finished a blog post explaining what to do.
You can use RC3 in 4.5.1 though.
Sweet, thanks man. I'll check out RC3 and turn off async. Cheers!
-- Nik
Slace,
That did it on the both the dups AND the casing. Thanks for poitning me to RC3 (at the time of this writing).
Cheer!
is working on a reply...