Skip to content
This repository has been archived by the owner on Mar 21, 2024. It is now read-only.

Commit

Permalink
Raise 1000 positions limit to 65535 for document attribute (#80)
Browse files Browse the repository at this point in the history
* Add specification file

* fix typos

* Update text/0077-words-position-limit.md

Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>

Co-authored-by: Clémentine Urquizar <clementine@meilisearch.com>
  • Loading branch information
gmourier and curquiza committed Nov 1, 2021
1 parent cd39626 commit 68c91cc
Showing 1 changed file with 33 additions and 0 deletions.
33 changes: 33 additions & 0 deletions text/0077-words-position-limit.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
- Title: Words position limit
- Start Date: 2021-10-06
- Specification PR: [#77](https://github.com/meilisearch/specifications/pull/77)
- Discovery Issue: [#202](https://github.com/meilisearch/product/issues/202)

# Words position limit

## 1. Functional Specification

### I. Summary

The purpose of this specification is to remove the limit of 1000 positions per attribute.

#### Summary Key points

- 1000 positions limit per document field is now raised at 65535.

### II. Motivation

We've seen many users denormalizing fields into multiple fields to index all the words because of the initial limit. This change will increases the limit to 65535, which should greatly reduce frictions on this issue. We expect to reduce the changes to be made to the document schema in order to use MeiliSearch more quickly and easily.

### III. Technical Explanations
n/a

## 2. Technical Aspects

When MeiliSearch indexes a document, it indexes several word positions per field until a limit is reached.

It is important to note that the limit is not strictly related to the number of words. Indeed, soft separators are also counted as `1` position while hard separators are counted as `8` positions.

## 3. Future Possibilities

- Expose a configurable default limit up to 65535.

0 comments on commit 68c91cc

Please sign in to comment.