Gravatar for steve.anderson@rbaconsulting.com

Question by Steve Anderson, Nov 11, 2015 3:45 PM

Multiple Item versions in index

Hello

Every so often we see items building up in the index that are the old versions items that have been updated in sitecore.

A fresh index reset will usually fix this, but is there something that I can be looking at as a possible cause?

Example: Only results matching the refine constraints are displayed. [Clear All]

sitecoreitem Prep-for-CNOR sitecore://database/web/itemid/{db55fbc7-c223-465b-ae67-18c363aecd48}/language/en/version/8 Details | Actions

sitecoreitem Prep-for-CNOR sitecore://database/web/itemid/{db55fbc7-c223-465b-ae67-18c363aecd48}/language/en/version/7 Details | Actions

sitecoreitem Prep-for-CNOR sitecore://database/web/itemid/{db55fbc7-c223-465b-ae67-18c363aecd48}/language/en/version/5 Details | Actions

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 11, 2015 7:34 PM

I see that you are using the Coveo .Net Front-End.

Which indexing solution are you using? Coveo for Sitecore or the Sitecore connector?

Gravatar for steve.anderson@rbaconsulting.com

Comment by Steve Anderson, Nov 12, 2015 8:48 AM

We are using Coveo for Sitecore. We see the duplicate results there too, which is what prompted me to dig further into the index, as I guessed it was a multiple version thing.

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 12, 2015 6:08 PM

I see… What is your Sitecore version (with revision number please) and your Coveo for Sitecore version (with build number)

Thanks

Gravatar for steve.anderson@rbaconsulting.com

Comment by Steve Anderson, Nov 12, 2015 6:34 PM

Here is the current config of this environment:

Sitecore Version: 8.0.150427 Sitecore.NET 8.0 (rev. 150427) April 27, 2015 .NET Framework 4.0.30319.34209

CES Version: 7.0 x64 Build 7711.0

Coveo for Sitecore Version: 3.0.1026.0

Coveo API Version: FileVersion=8.0.543.0 SearchApiLibVersion=8.0.396.13

Thank You

Gravatar for jflheureux@coveo.com

Comment by Jean-François L'Heureux, Nov 16, 2015 2:55 PM

I see that you have:

  • The May 2015 release of Coveo for Sitecore
  • The June 2015 edition of Coveo Enterprise Search and Coveo Search API

Normally, the 3 software should be on the same monthly version to ensure it works correctly. Can you upgrade your Coveo for Sitecore package to the June 2015 release as well?

Other than that:

  • When Sitecore create a new version of an item in the master database, it indexes that item in the master indexes. It indexes all the versions of the item at once, including the new version. So it's normal to have many versions in the master index.
  • When Sitecore automatically publishes an item from a workflow action "Sitecore.Workflows.Simple.PublishAction", it does ask the search providers to remove the older versions of that item in the web index, which Coveo does automatically.
Gravatar for steve.anderson@rbaconsulting.com

Comment by Steve Anderson, Nov 17, 2015 3:49 PM

So, I knew that we were back a version on the release for Coveo for Sitecore. The reason for this was simply that there were some changes to some imagery (sprites) and .js that the Coveo search components were using, and we did not wish to re-code our modifications to work with them.

That said, I suppose that we can if we must, but I am not convinced that will help much. The error that we see seems to be simply that when we publish, it does not remove the older versions from the index. Any thoughts on what I might be looking for in the logs, and/or is there some specific configuration that I should be using for both Master and Web? In reality, I do not even want multiple versions in the Master index.

Gravatar for steve.anderson@rbaconsulting.com

Comment by Steve Anderson, Dec 11, 2015 11:06 AM

Or, how about in the logs. Since this seems to be somewhat sporadic, is there anything that I can look for in any of the logs around this failing to remove older versions?

0 Reply
Ask a question