Azure Search 1000 field limit issue
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
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
add a comment |
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
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
add a comment |
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
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
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
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
asked Jan 2 at 15:06
Ken McAndrewKen McAndrew
2,336527
2,336527
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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>
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
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
Jan 2 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/…
– Bart Verdonck
Jan 2 at 16:06
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
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>
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
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
Jan 2 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/…
– Bart Verdonck
Jan 2 at 16:06
add a comment |
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>
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
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
Jan 2 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/…
– Bart Verdonck
Jan 2 at 16:06
add a comment |
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>
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
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>
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
answered Jan 2 at 16:00
Bart VerdonckBart Verdonck
1,351120
1,351120
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
Jan 2 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/…
– Bart Verdonck
Jan 2 at 16:06
add a comment |
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
Jan 2 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/…
– Bart Verdonck
Jan 2 at 16:06
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
Jan 2 at 16:02
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
Jan 2 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/…
– Bart Verdonck
Jan 2 at 16:06
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
Jan 2 at 16:06
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
