You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
It happens when a few documents are modified in a bigger DB, so the incremental facet update kicks in.
The real fix is to rework the incremental facet update; many have started (or will start) work in this area.
A workaround is to do a 1.6.2 with incremental facet update disabled and only bulk facet update enabled.
Expected behavior
Faceted documents, when their facets are modified, must be ordered correctly, whether they are strings or numbers, which doesn't matter either.
Meilisearch version:
All versions with the incremental indexing: v1.6.0 and v1.6.1.
The text was updated successfully, but these errors were encountered:
4408: Disable incremental facet update as a stop gap r=Kerollmops a=dureuill
# Pull Request
Temporarily disable incremental facet update to fix issue related with out-of-order sorts.
## Related issue
Workaround for #4409
## What does this PR do?
- Always use bulk insert to insert facet values
Co-authored-by: Louis Dureuil <louis@meilisearch.com>
4433: Enhance facet incremental r=Kerollmops a=ManyTheFish
# Pull Request
## Related issue
Fixes#4367Fixes#4409
## What does this PR do?
- Add a test reproducing #4409
- Fix#4409 by removing a document from a level only if it is no more present in all the linked sub-level nodes
- Optimize facet Incremental indexing by creating or deleting a complete level once per field id instead of for each facet value
- Optimize facet Incremental indexing by doing the additions and the deletions in the same process instead of doing them separately
Co-authored-by: ManyTheFish <many@meilisearch.com>
When modifying a small number of documents, they appear in the wrong order.
Related to #4374, #4339, and #4390.
To Reproduce
It happens when a few documents are modified in a bigger DB, so the incremental facet update kicks in.
The real fix is to rework the incremental facet update; many have started (or will start) work in this area.
A workaround is to do a 1.6.2 with incremental facet update disabled and only bulk facet update enabled.
Expected behavior
Faceted documents, when their facets are modified, must be ordered correctly, whether they are strings or numbers, which doesn't matter either.
Meilisearch version:
All versions with the incremental indexing: v1.6.0 and v1.6.1.
The text was updated successfully, but these errors were encountered: