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

A suggestion about field size problem #187

Open
azhu021 opened this issue Aug 17, 2024 · 0 comments
Open

A suggestion about field size problem #187

azhu021 opened this issue Aug 17, 2024 · 0 comments
Assignees

Comments

@azhu021
Copy link

azhu021 commented Aug 17, 2024

Thanks for your great plugin. I'm not very good at English. I hope you can understand what I said below.

Description

I think you can split the contentStripTruncate attribute into two or more attributes to break the size limitation.

Explanation / motivation

My problem:
When a post exceed about 5000 strings. I will encountered an error INFO Error has occurred during indexing posts : [object Object] when deploying my Hexo site.

My configuration:
chunkSize: 5000
fields:
- content:strip:truncate,0,5000

My current solution:
I reduced the size of the contentStripTruncate attribute as blow:
- content:strip:truncate,0,2000

The error has disapeared now. But I also can't search the full artical content. It is not friendly for my visitors.
I think you can split the content of the contentStripTruncate attribute into two or more attributes as long as the total size of one record didn't exceed 10kb limit set by the algolia.

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