v0.21.0rc0

⚠️ WARNING:

• This version involves a lot of internal changes; it means some bugs might be present.
• This RC version might have weird behavior with highlighting. It will be fixed in the official v0.21.0 release.
• Since it's an RC (release candidate) we do not recommend using this version in production.

Please feel free to report the bugs you find out and give your feedback in issues. Precise you are using the v0.21.0rc0 version!
The whole MeiliSearch team thanks you in advance for your help and your patience! ❤️

💡 Visit our temporary docs for the v0.21.0. It's not completely finished yet, but it will help you try the v0.21.0 with your own dataset!

You can test this release by downloading the binaries available in this release.
Or you can use it with docker:

docker run -p 7700:7700 getmeili/meilisearch:v0.21.0rc0 ./meilisearch

Improvements

• New Web UI
• Facets with numbers
• Criterion words is available
• Search performance improvements
• Highlight arrays and objects
• Phrase search (" around words in a search query)
• Usage of facet and filter during the search is simplified (see paragraph below)
• Reduce RAM usage during indexation
• A lot of bug fixes

Breaking change

• filters and facetsFilter parameters (during search) are removed and replaced by the unique filter parameter.
  
When using filter, the genre: comedy syntax is not available. Use genre = comedy instead. The result will be the same as in the previous versions.
  Both syntaxes are available:

  • string: 
"filter": "genre = comedy AND price > 13"

  • or array: 
"filter": ["genre = comedy", "price > 13 "]

• To be used in the filter parameters, an attribute has to be set in filterableAttributes.
• The settings attributesForFaceting is renamed as filterableAttributes
• fieldsDistribution is now fieldDistribution in the stats routes
• The new default ranking rules are:


[
  "words",
  "typo",
  "proximity",
  "attribute",
  "exactness"
]

Meilisearch v0.20.0

Breaking changes:

• /health route now returns 200 instead of 204
• the root route / now returns 200 when being in a production environment

Fixes

• Fix snapshot temp file
• Fix URL when launching MeiliSearch
• several mini dashboard fixes

Pre-release v0.20.0-rc8

Merge #1309

1309: fix snapshot r=MarinPostma a=MarinPostma

fix snapshot broken by #1238.

Co-authored-by: mpostma <[email protected]>
Co-authored-by: Marin Postma <[email protected]>

Pre-release v0.20.0-rc5

Merge #1310

1310: Fix display of http address r=MarinPostma a=curquiza

Wrong display introduced by https://github.com/meilisearch/MeiliSearch/pull/1206

Now displaying:

<img width="968" alt="Capture d’écran 2021-03-26 à 12 04 59" src="https://user-images.githubusercontent.com/20380692/112622594-8c173080-8e2b-11eb-81c3-5876d273e5fa.png">


Co-authored-by: Clémentine Urquizar <[email protected]>

Pre-release v0.20.0-rc10

Merge #1315

1315: fix armv7 r=MarinPostma a=MarinPostma

fix armv7 build

this was caused by usize being 32 bit on armv7 and 64bits on all other targeted architectures.


Co-authored-by: Marin Postma <[email protected]>

Pre-release v0.20.0-rc2

Merge #1307

1307: change ubuntu version r=MarinPostma a=MarinPostma

Change the CI ubuntu version from `latest` to `18.04` because `latest` uses a too recent version of glibc, preventing meilisearch from running on the debian version of the DO image


Co-authored-by: mpostma <[email protected]>

Pre-release v0.20.0-rc0

Cf changelogs and the milestones.

The v0.20.0 release is out next Monday (29/03/2021)

Meilisearch v0.19.0

Merge branch 'release-v0.19.0' into stable

Pre-release v0.19.0-rc4

Merge #1224

1224: fix synonyms normalization r=MarinPostma a=LegendreM

Synonyms needs to be indexed in ascendant order,
and the new normalization step for synonyms potentially changes this order
which break the indexation process
because "Harry Potter" > "HP"  but "harry potter" < "hp"

Co-authored-by: many <[email protected]>

Pre-release v0.19.0-rc2

Merge #1222

1222: Ignore existing primary key r=Kerollmops a=MarinPostma

fixing bug in #1176 made it an hard error to try to re-set the primary key on a document addition. This PR makes Meilisearch ignore a primary key passed as an argument to a document addition. This has been decided after a discussion with @curquiza, in order to make the bug fix non breaking.

Turns out it was a good catch too, since contrary to what I thought the error was not caught asynchronously, thank you @curquiza 

Co-authored-by: mpostma <[email protected]>