meilisearch / meilisearch/documentation
Document max_fields_limit_exceeded
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 174
- Forks
- 276
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
Some users have encountered a max_fields_limit_exceeded erros, and they usually think it's related to the maximum number of attributes per document, but it's not.
According to @Kerollmops:
this issue is related to the total number of field over all the documents. Most of the time it is due to people storing user names in a nested object. The engine understand those as fields. There is a maximum of 64k different fields.
{ "users": { "kero": 1, "tamo": 2, ... } }.
See open issue.
It's a current engine limitation, so I thought it should be documented.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Known Limitations page and review the related Meilisearch issue for the meaning of max_fields_limit_exceeded. Document that the limit applies to 64k distinct fields across all documents, including dynamic keys in nested objects, and distinguish it from the per-document attribute limit.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100