Developer forum

Forum » Ecommerce - Standard features » Buildning new index never ends

Buildning new index never ends

Lars Larsen
Reply

Hi,

I have set up an index based on the new Lucene index. When I start the build of the index the process never ends! What can be wrong? The status page shows some strange figures (see attachment).

Capture.PNG

Replies

 
Nicolai Høeg Pedersen
Reply

Hi Lars

1,2 mio products in 6 minutes is good! Can you provide a link so we can have a look?

Nicolai

 
Lars Larsen
Reply

Hi Nicolai

Thanks, here is a link

 
Nicolai Høeg Pedersen
Reply

Hi Lars

This is due to the solution is still running 8.6.1.1 - it has the error of the casing of AutoId vs. AutoID in the database.

BR Nicolai

 
Lars Larsen
Reply

Hi Nicolai

I have just upgraded from 8.6.1.10 to 8.6.1.12 and now the casing problem is back! Building the index (on 8.6.1.12) newer ends if the AutoId field is spelled "ProductAutoId". But if I change the casing (in the database - table EcomProducts) to "ProductAutoID" the build process succeeds.

 
Nicolai Høeg Pedersen
Reply

Hi Lars

The code is in 8.6.1 branch. Sure you have not messed up your bin folder?

NP

 
Lars Larsen
Reply

Hi Nicolai

This is really strange. Now I can't reproduce the scenario from the 26. of June. Now when rebuilding the index never ends regardless of the casing of "Id" in the EcomProducts table when running 8.6.1.12. Switching to 8.6.1.10 it works! I'm pretty sure my bin folder is not messed up because I'm running the site with the folder "Application(8.6.1.10) or Application(8.6.1.12)" as the root folder (standard setup). I'm using the same database with the two DW version.

 
Nicolai Høeg Pedersen
Reply

Hi Lars

Can you provide us a link please.

BR Nicolai

 
Lars Larsen
Reply

Hi Nicolai

Here is a link: motostore.dis-play.dk

/Lars

 
Nicolai Høeg Pedersen
Reply
This post has been marked as an answer

Hi Lars

Will you try 8.6.1.14 - it seems like there was a merge error of this bug in .13. Still the casing on the autoid I think...

Or give us full access to the solution.

BR Nicolai

Votes for this answer: 1
 
Lars Larsen
Reply

Hi Nicolai

I upgraded to v8.6.1.14 and now it works. Thanks :-)

 

You must be logged in to post in the forum