Algolia indexing not continuing when a page size is to large

[gerrit-de-heij]

I get an error when a page is to large for Algolia to index (20kb for example). The build process of the index doesn't continue with indexing the rest of the pages. I need it to skip the pages that are to large in size and index all other pages. Is there a setting that I can change so the build process skips the pages that are to large and index the rest of the pages?

---

This item has been added to our backlog AB#49904

[acoumb]

Hi @gerrit-de-heij ,

Have you checked the logs for errors, whether a specific property using a complex type is throwing an exception? Because in this case you can add your own custom converter to address the matter.

Thanks,
Adrian

[gerrit-de-heij]

Hi @acoumb ,

I currently don't have time to see if this helps to solve the problem. But I think writing a custom converter for a BlockGrid is still not going to fix the issue, because a BlockGrid can still contain a lot of text. When it does, it still isn't indexed by Algolia and neither are the rest of the pages after that, because it gives the error. Isn't there a way to continue indexing the rest of the pages when one page is to large?

Thanks in advance!

[acoumb]

Hi @gerrit-de-heij ,

Could you try again with latest versions of Algolia? Also, which version of Umbraco are you using?

Thanks,
Adrian

[gerrit-de-heij]

Hi @acoumb ,

I'm currently working with Umbraco version 13.8.1. I'm going on vacation this week so I can't try this out myself, but I think one of my colleagues has time to try this again with the latest version of the package. They will let you know if this solved the issue.

Thanks for the update!

Gerrit

[gerrit-de-heij]

@acoumb,

I now have installed the latest version of the package (version 2.3.2) that supports my Umbraco version (which now is Umbraco 13.9.2), but it seems there still isn't an option for continuing the indexing when a page exceeds the Algolia index item limit of 10KB.

But I have another problem: I have created a test converter for the BlockGrid which sets the value of the BlockGrid's to "TEST". Now when I go to my Algolia dashboard and look at the records inside the index, the following data is displayed for one page:

The site is a multilingual site and this content node is variet by culture. The value of the BlockGrid is stored for every language in one index record. This causes the JSON value to be very large which exceeds the record limit easily.

Is there a way to let the package create one record for each language variant of a content node instead of saving all language variants content in one Algolia record?

Thanks in advance!

Gerrit

[gerrit-de-heij]

Hi @acoumb, is there any news regarding this issue? We need this to be fixed soon, because now our client can't use Algolia properly.

Thanks in advance!

Gerrit

[acoumb]

Hi @acoumb , I will try to address this in the first weeks of November.

[acoumb]

hi @gerrit-de-heij , could you install the latest patch update of Algolia and let me know if the issue persists?
thanks