Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Algolia index size limit #248

Open
RomanSpeak opened this issue Feb 17, 2025 · 1 comment
Open

Algolia index size limit #248

RomanSpeak opened this issue Feb 17, 2025 · 1 comment

Comments

@RomanSpeak
Copy link

The issue:
We want to be able to index our grid in order to make use of the full potential for Algolia searching. Unfortunately we get the following message during the build action (xyz is our page key);

An error has occurred while building the index: {"message":"Record at the position 146 objectID=xyz is too big size=94224/10000 bytes. Please have a look at https://www.algolia.com/doc/guides/sending-and-managing-data/prepare-your-data/in-depth/index-and-records-size-and-usage-limitations/#record-size-limits","position":146,"objectID":"xyz","status":400}

We could upgrade to the paid plan, but we are afraid that some pages might exceed even the upgraded size limit of 100kb. Does the Algolia integration already apply chunking, or is there a way that we could properly split the Block Grid widgets into chunks? The pages are vary by culture with a decent amount of languages, is it possible that the issue might originate from that? The blockgrid is visually not very large, consisting of about 7 rows and a total of ~12 widgets.

Let me know if this is a known issue, or if there is a solution!

Using:

  • Umbraco 13.6.0
  • Algolia 2.3.1
@acoumb
Copy link
Contributor

acoumb commented Mar 10, 2025

Hi @RomanSpeak ,

Have you considered using custom converter to handle complex data before sending it to Algolia?

Thanks,
Adrian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants