Meilisearch v0.21.0 — Release Notes & Engineering Impact

## Breaking changes - The index setting `attributesForFaceting` has been renamed to `filterableAttributes` - The `filters` and `facetsFilter` search parameters are replaced by `filter` To use the `filter` search parameter, you must add the attribute you want to filter on to the `filterableAttributes` index setting. Only use the `=` syntax (e.g. `genres = comedy`). Filter expressions using the `:` syntax (e.g. `genres: comedy`) are deprecated. Filter expressions can be combined as strings or nested arrays: - string: 
`"filter": "genre = comedy AND price > 13"
` - array: 
`"filter": ["genre = comedy", "price > 13 "]
` - When using the `filter` search parameter on an array, the operator `!=` will only return results that do not contain the value - The new default ranking rules are: ```json 
[ "words", "typo", "proximity", "attribute", "exactness" ] ``` - `fieldsDistribution` has been renamed to `fieldDistribution` - Rename `MAX_MDB_SIZE` environment variable and `--max-mdb-size` option flag to `MAX_INDEX_SIZE` and `--max-index-size` - In the route `/version`, `buildDate` is now named `commitDate` and format has changed. MeiliSearch is now reproducible ## Improvements - New Web UI - Facets with numbers - Criterion `words` is available - Search performance improvements - `attributesToHighlight` now highlights matches inside arrays and objects - Phrase search (`"` around words in a search query) - Reduced RAM usage during indexation - Removed the limit of 200 indexes per database - Support typo on the first letter - Facet distribution also works on arrays - Enhanced logging capabilities with `MEILI_LOG_LEVEL` environment variable and `--log-level` option. Debug level now outputs query and search results - Analytics (Amplitude and Sentry) are now unified and can be disabled at once with `MEILI_NO_ANALYTICS` and `--no-analytics` flag - Improved `exactness` ranking rule - A new update status, `processing`, has been added - Add fields `startedAt` and `finishedAt` information on the route `/dumps/{dump_id}/status`. - Cropping is now consistent - Users can specify the payload limit size unit (e.g. Kb, Mb, Gb) - Improve `/stats` route speed - Improve compilation time with a caching strategy - Renamed branch `master` into `main`. - Improved README ## Fixes - Fix dumps bug that would exclude attributes not present in `displayedAttributes` from the dump file - Fix error on snapshots when the user enters a wrong path - Fix number of calculated hits when a distinct field is set - Fix CORS error when authentication is missing - Windows instances only take as much space as necessary now