Update getmeili/meilisearch Docker tag to v1.45.2 #1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/getmeili-meilisearch-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v1.43.1→v1.45.1Release Notes
meilisearch/meilisearch (getmeili/meilisearch)
v1.45.1: 🦒Compare Source
🪲 Bug Fixes
Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.45.0...v1.45.1
v1.45.0: 🦒Compare Source
Meilisearch v1.45.0 mainly improves indexing performance when changing settings and also improves document fetch performance.
✨ Enhancement
While Meilisearch tries to improve indexing speed when users add documents and mix those additions with deletions via a filter, it is still an anti-pattern to interleave both. It is recommended to delete documents by ID whenever possible, as the engine is optimized to merge them, thereby drastically speeding up indexation.
We are introducing support for more settings in the nez settings indexer. If you find any bugs, please report them on GitHub. You can disable the new settings indexer by setting the environment variable like this:
MEILI_EXPERIMENTAL_NO_EDITION_2024_FOR_SETTINGS=trueor use the equivalent dedicated CLI parameter.Changing one of the following settings is now directly handled by the new settings indexer: displayed fields, synonyms, the primary key, authorize typos, min word len one and two typos, max values per facet, sort facet values by, pagination max total hits, search cut off, chat, and foreign keys.
Meilisearch can use the new settings indexer when the settings change the facet search root boolean parameter.
🪲 Bug Fixes
We fixed an issue where users were changing the binary-quantized boolean in embedder configurations. The change corrupted the database, making it impossible to change the quantization in the future. Users had to create a binary-quantized embedder from scratch, or they could never change it again.
🔩 Miscellaneous
Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.44.0...v1.45.0
v1.44.0Compare Source
Meilisearch v1.44.0 adds remote federated facet search, indexing performance improvements, and other improvements and bugfixes. It also contains a couple of breaking changes, detailed below.
Breaking changes
networkexperimental feature, with sharding enabled (leaderis notnullin the network configuration),POST /indexes/{indexUid}/facet-searchcalls now default to a remote federated facet search, fetching and merging results from all shards in the network.searchCutOffMsdefined in the index, rather than fixed.🌈 Improvements
Remote facet search
Meilisearch now has the ability to search across all shards of a network during facet search via the existing dedicated facet search route.
networkexperimental feature and have aleaderdefined for your network, remote calls are now the default for calls toPOST /indexes/{indexUid}/facet-searchuseNetworkparameter of the facet search object.By @dureuill in https://github.com/meilisearch/meilisearch/pull/6375
Reduce memory usage of the indexing
Reduces allocated memory when computing prefixes and speeds up some operations to avoid unnecessary deserialization.
If you still see high memory usage while the engine is post-processing, we recommend using the
--experimental-reduce-indexing-memory-usageoption.By @Kerollmops in https://github.com/meilisearch/meilisearch/pull/6334
Improve GeoJSON indexing performance
This PR upgrades the
cellulitelibrary to a version that includes a GeoJSON indexing optimization. With this change, GeoJSON indexing avoids reprocessing documents that were already indexed in dense cells, and only handles newly added documents incrementally as they descend through the recursive cell tree.By @YoEight in https://github.com/meilisearch/meilisearch/pull/6374
Human-formatted sizes and detailed DB sizes in stats
Adds two new query parameters to
GET /indexes/{indexUid}/statsandGET /stats:showInternalDatabaseSizes: boolean, optional, defaults tofalse. When present, the index stat objects in responses of the stat routes now contain an additionalinternalDatabaseSizeskey, whose value is a dictionary of the internal database names and their current size in the index, like in the stats object of a batch.sizeFormat:humanorraw: optional, defaults toraw. When present and set tohuman, then all database sizes in responses of the stat routes will be returned as a string containing an appropriate unit (MiB, GiB, etc). When missing or set toraw, then the current behavior of expressing the size in bytes as a number is retained.Note for integrations: The keys in
internalDatabaseSizesare subject to change and should not be exposed as a strongly typed object. This is the same as the existinginternalDatabaseSizesin batch stats.Adding
showInternalDatabaseSizesto an index statsAdding
showInternalDatabaseSizesandsizeFormat=humanto global statsThe call without any parameters is the same as in previous versions.
By @dureuill in https://github.com/meilisearch/meilisearch/pull/6338
🦋 Fixes
🔩 Miscellaneous changes
New Contributors
Full Changelog: https://github.com/meilisearch/meilisearch/compare/v1.43.1...v1.44.0
Configuration
📅 Schedule: (in timezone Europe/Berlin)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
chore(deps): update getmeili/meilisearch docker tag to v1.45.1to Update getmeili/meilisearch Docker tag to v1.45.16911aecfdebdc3cfc0fbUpdate getmeili/meilisearch Docker tag to v1.45.1to Update getmeili/meilisearch Docker tag to v1.45.2View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.