Sitecore 8.2 Azure PaaS and Lucene

This is a short blog sharing my first experience with deploying onto Azure PaaS in regard to indexing.

tldr

Azure PaaS does not support Lucene search, only Azure Search (configured by default), Solr or Coveo.

I have added an update at the end showing that you can actually use Lucene but requires manual work.

Symptoms of the problem

We deployed our Sitecore 8.2 project to Azure and everything seems fine, until we tried to open a page that uses indexing, which crashed. I remembered that we still haven’t rebuilt our custom indices yet. So I tried to but it kept completing right away. It should take at least 20 minutes, but it was completing immediately.

Diagnosis

I search google, looked at my custom configs again and checked what other reasons could’ve caused this but couldn’t find anything. I added a question to sitecore.stackoverflow.com and within few minutes I got the answer from @Tamas that Azure PaaS does not support Lucene. It only supports Azure Search, Solr and Coveo.

Solution

Luckily, the solution was really easy, simply copy the contents of the sitecore_master_index configuration file (Sitecore.ContentSearch.Azure.Index.Master.config) into your custom index file and update it accordingly. I’m not going to share the contents of the file since it may change between versions.

Important Note

It seems Azure Search does not support field names that start with numbers whereas Lucene did. I had to rename a couple of fields, so be careful.

 

Update (15/10/2017)

Azure Search is so messy with Sitecore. All my search-using features did not work correctly after switching to Azure Search and I couldn’t know why. Azure Search also doesn’t support fieldnames starting with underscore. Although Sitecore has updated the configs for this, but I still had issues with fieldnames.

With the deadline almost here, I couldn’t fix the search using Azure Search, so I forced Lucene to work on Azure by accessing my Sitecore installations using ftp, disabling all Azure Search configs and enabling Lucene configs. I had to do this on both CM and CD of course. All I had to do is follow the ‘Set up configuration files’ section in this article and do the reverse.

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s