examine issues

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Rich Green 2246 posts 4008 karma points

Oct 21, 2010 @ 11:35

0

Examine issues

I've been trying out Examine under the following conditions:

4.5.2 with RC3

4.5.2 with RTM 1.0 (with internal indexer changed to StandardAnalyser)

The conclusion is that the index is not getting updated correctly unless I reset IIS.

There are no errors in the log table.

The results were the same for RC3 and RTM 1.0

Here are my tests using clean Runway install 4.5.2 Application pool in Integrated (couldn't get it to run under Classic) under v1.0 RTM.

1. First load of index - Perfect

2. Rename 'modules' to 'nitros' and publish - Index Not Updated

3. Publish node again - 'Nitros' gets added but 'modules' still in index

4. Publish node again - 'modules' still in index and Rank for 'Nitros' goes up to 2

5. Reset IIS at this point - Log Table

6. Perfect

I'm not exactly sure what is the expected behaviour as I don't know how and when the index is updated, but the event that gets run after IIS Reset seems to solve all the issues.

Any thoughts would be appreciated.

Rich

Copy Link
Aaron Powell 1708 posts 3046 karma points c-trib

Oct 22, 2010 @ 00:00

0

Are you running async on or off?

Copy Link

Rich Green 2246 posts 4008 karma points

Oct 22, 2010 @ 00:17

runAsync="true"

<Examine>
  <ExamineIndexProviders>
    <providers>
      <add name="InternalIndexer" type="UmbracoExamine.LuceneExamineIndexer, UmbracoExamine"
           runAsync="true"
           supportUnpublished="true"
           supportProtected="true"
           interval="10"
           analyzer="Lucene.Net.Analysis.Standard.StandardAnalyzer, Lucene.Net"/>
      <add name="InternalMemberIndexer" type="UmbracoExamine.MemberLuceneExamineIndexer, UmbracoExamine"
           runAsync="true"
           supportUnpublished="true"
           supportProtected="true"
           interval="10"
           analyzer="Lucene.Net.Analysis.Standard.StandardAnalyzer, Lucene.Net"/>
    </providers>
  </ExamineIndexProviders>
  <ExamineSearchProviders defaultProvider="InternalSearcher">
    <providers>
      <add name="InternalSearcher" type="UmbracoExamine.LuceneExamineSearcher, UmbracoExamine"
           analyzer="Lucene.Net.Analysis.Standard.StandardAnalyzer, Lucene.Net"/>
      <add name="InternalMemberSearcher" type="UmbracoExamine.LuceneExamineSearcher, UmbracoExamine"
           analyzer="Lucene.Net.Analysis.Standard.StandardAnalyzer, Lucene.Net" enableLeadingWildcards="true"/>           
    </providers>
  </ExamineSearchProviders>
</Examine>

Rich

Copy Link

Aaron Powell 1708 posts 3046 karma points c-trib

Oct 22, 2010 @ 08:21

0

If async is true you wont get any error logs, it runs outside the HttpContext so the error logging doesn't work.

How long are you waiting between publishing and inspecting with Luke? Is there anything in your Queue folder?

Copy Link
Rich Green 2246 posts 4008 karma points

Oct 22, 2010 @ 15:49

0

Thanks for your reply slace, I need to do some further testing as I was getting problems with my Umbraco.Config file getting the old fields too.

Seems like a permission error could have caused both issues.

Copy Link
is working on a reply...

Please Sign in or register to post replies

Flag this post as spam?