MeiliSearch/milli
Jakub Jirutka 13f1277637 Allow to disable specialized tokenizations (again)
In PR #2773, I added the `chinese`, `hebrew`, `japanese` and `thai`
feature flags to allow melisearch to be built without huge specialed
tokenizations that took up 90% of the melisearch binary size.
Unfortunately, due to some recent changes, this doesn't work anymore.
The problem lies in excessive use of the `default` feature flag, which
infects the dependency graph.

Instead of adding `default-features = false` here and there, it's easier
and more future-proof to not declare `default` in `milli` and
`meilisearch-types`. I've renamed it to `all-tokenizers`, which also
makes it a bit clearer what it's about.
2023-05-04 15:45:40 +02:00
..
examples Improve performance of the cheapest path finder algorithm 2023-05-02 09:59:42 +02:00
src Allow to disable specialized tokenizations (again) 2023-05-04 15:45:40 +02:00
tests Merge remote-tracking branch 'origin/main' into search-refactor 2023-05-03 12:19:06 +02:00
Cargo.toml Allow to disable specialized tokenizations (again) 2023-05-04 15:45:40 +02:00
README.md Add a README to the milli crate 2023-01-16 16:25:12 +01:00

the milli logo

a concurrent indexer combined with fast and relevant search algorithms

Introduction

This crate contains the internal engine used by Meilisearch.

It contains a library that can manage one and only one index. Meilisearch manages the multi-index itself. Milli is unable to store updates in a store: it is the job of something else above and this is why it is only able to process one update at a time.