Azure Search 1000 field limit issue












3














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?






azure-search







share|improve this question



























    3














    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?






    azure-search







    share|improve this question

























      3












      3








      3


      1





      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?






      azure-search







      share|improve this question













      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?






      azure-search




      azure-search






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 7 hours ago









      Ken McAndrew

      2,321527




      2,321527






















          1 Answer
          1






          active

          oldest

          votes


















          4














          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>





          share|improve this answer





















          • 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.
            – Ken McAndrew
            6 hours ago










          • 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/…
            – Bart Verdonck
            6 hours ago













          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "664"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15796%2fazure-search-1000-field-limit-issue%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          4














          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>





          share|improve this answer





















          • 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.
            – Ken McAndrew
            6 hours ago










          • 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/…
            – Bart Verdonck
            6 hours ago


















          4














          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>





          share|improve this answer





















          • 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.
            – Ken McAndrew
            6 hours ago










          • 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/…
            – Bart Verdonck
            6 hours ago
















          4












          4








          4






          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>





          share|improve this answer












          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>






          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 6 hours ago









          Bart Verdonck

          1,216119




          1,216119












          • 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.
            – Ken McAndrew
            6 hours ago










          • 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/…
            – Bart Verdonck
            6 hours ago




















          • 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.
            – Ken McAndrew
            6 hours ago










          • 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/…
            – Bart Verdonck
            6 hours ago


















          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.
          – Ken McAndrew
          6 hours ago




          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.
          – Ken McAndrew
          6 hours ago












          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/…
          – Bart Verdonck
          6 hours ago






          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/…
          – Bart Verdonck
          6 hours ago




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Sitecore Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f15796%2fazure-search-1000-field-limit-issue%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Eastern Orthodox Church

          Image
          Not to be confused with Oriental Orthodoxy, Eastern Christianity, or Eastern Catholic Churches. "Eastern Orthodoxy", "Orthodox Church", "Orthodox Catholic Church", and "Orthodox Christian Church" redirect here. For other uses, see Orthodox (disambiguation). This article may be too long to read and navigate comfortably . The readable prose size is 132 kilobytes. Please consider splitting content into sub-articles, condensing it, or adding or removing subheadings. ( January 2018 ) Part of a series on the Eastern Orthodox Church Mosaic of Christ Pantocrator, Hagia Sophia Overview Structure Theology (History of theology) Liturgy Church history Holy Mysteries View of salvation View of Mary View of icons Background Crucifixion / Resurrection / Ascension of Jesus Christianity Christian Church Apostolic succession Four Marks of the Church Orthodoxy Organization Autocephaly Patriarchate ...
          Read more

          Zagreb

          Image
          This article is about the Croatian capital city. For other uses, see Zagreb (disambiguation). City in City of Zagreb, Croatia Zagreb City Grad Zagreb City of Zagreb Clockwise, from top: St. Mark's Square, Croatian State Archives, Zagreb Tram, Art Pavilion, Cibona & HOTO towers and Croatian National Theatre. Flag Coat of arms Zagreb Location of Zagreb in Croatia Show map of Croatia Zagreb Zagreb (Europe) Show map of Europe Coordinates: 45°49′N 15°59′E  /  45.817°N 15.983°E  / 45.817; 15.983 Coordinates: 45°49′N 15°59′E  /  45.817°N 15.983°E  / 45.817; 15.983 Country   Croatia County City of Zagreb RC diocese 1094 Free royal city 1242 Unified 1850 Subdivisions 17 city districts 218 local committees (70 settlements) Government  • Type Mayor-Council  • Mayor Milan Bandić (BM 365)  • City Assembly 51 members BM 365, ZL, NS-R (14) SDP, GLAS, HNS, HSS, NH-PS (13) ...
          Read more

          Understanding the information contained in the Deep Space Network XML data?

          Image
          up vote 1 down vote favorite NASA's Deep Space Network activity can be viewed conveniently at https://eyes.nasa.gov/dsn/dsn.html but if you would like data in a more raw XML form, it can be accessed as described in this answer Below is a small Python script that reads the XML into a list of dictionaries, and saves it to disk as a JSON. The dictionaries are organized at the higher level by dish, then by spacecraft per dish. Question: What are the most-likely meanings of all the data field contained in the Deep Space Network XML data? This is the example url from the other answer, used in the script below: https://eyes.nasa.gov/dsn/data/1365107113.xml def dictify(r,root=True): # https://stackoverflow.com/questions/2148119/how-to-convert-an-xml-string-to-a-dictionary-in-python/30923963#30923963 if root: ret...
          Read more