simple slicer to circumvent the 10k limit #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a proposed fix to circumvent the 10k limit on a single entity in an Algolia search index. Since each entity can only be 10k in size, you get a rejection when trying to index large streamfields. This adds a basic slicer that slices the page content into < 10k chunks and appends a suffix to the objectID. Since the number of entities in an index is not a problem you can then add all those chunks as seperate entities and use distinct to prevent duplicates in search results.