10

I noticed in 9.0.2 and 9.1 there's a new ExcludeFields.config file for the Azure indexes to help keep things below Azure's 1000-field limitation. However, this apparently isn't enough, as we're running into the issue. I saw an SSE post on this - https://stackoverflow.com/questions/49940421/sitecore-9-1-azure-master-index-rebuild-gets-stuck - which I assume meant 9.0.1 given the time of the issue. Has anyone run into a better way to handle this, or generally is the best way to exclude all of the custom fields in templates I'm creating and make custom indexes for the specific areas I'm working with?

2
  • FYI - there is an Azure feature request to increase Azure's hard limit. Go give it a vote, if you're so inclined. May 23 '19 at 19:46
  • Since I get alerts that this question is so popular, I should note that as of Sitecore 10.2, Azure Search will be removed from the product; it was marked deprecated when Sitecore 10 was released. Feb 18 at 13:07
11

The problem is that when you are adding fields and have a bunch of languages, this will create a lot of new fields when "indexallfields" is set to true. (Each field multiplied by the number of languages) So you quickly get over 1000 fields. And since the 1000 fields is an azure limitation, there is not much sitecore can do about it.

The best way to handle this is still to set indexallfields to false and to include the fields you need in the master index manually.

With 9.1, there is no need to add the form fields anymore, this has been solved by Sitecore.

<sitecore role:require="Standalone or ContentManagement or ContentDelivery" search:require="Azure">
<contentSearch>
  <indexConfigurations>
    <defaultCloudIndexConfiguration>
      <documentOptions>
        <!-- We only want default fields in the core/master/web indexes on azure due to 1000 field limit  -->
        <indexAllFields>false</indexAllFields>            
      </documentOptions>
    </defaultCloudIndexConfiguration>
  </indexConfigurations>
</contentSearch>
</sitecore>
4
  • Any way this can be patched back to 9.0.2, or is that solution only applicable to 9.1? Thanks for the other info. Jan 2 '19 at 16:02
  • Sure, you can use this on 9.0.2 as well, however for 9.0.2 you need to add some fields for forms to work. Have a look at this post for the fields. sitecore.stackexchange.com/questions/12700/… Jan 2 '19 at 16:06
  • Is there a list of out-of-the-box fields that must be indexed for Sitecore to function ? I'm concerned that if I exclude all fields it will cause unexpected issues to arise if the included field list is not comprehensive.
    – andyp
    Feb 6 '19 at 1:54
  • When you set indexAllFields to false, sitecore will still index the minimum fields it requires. Feb 6 '19 at 9:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.