[Tracking-issue] Settings diff-indexing #4493
Labels
performance
Related to the performance in term of search/indexation speed or RAM/CPU/Disk consumption
settings diff-indexing
Issues related to settings diff-indexing
tracking issue
Tracks development of a global issue
Related product team resources: PRD (internal only)
Motivation
The indexing process is split into several parts, extracting different data from the documents depending on the settings.
Each extraction can be precisely linked to one or several settings when running indexing, but Meilisearch v1.7 and older versions reindex everything like it was fresh indexing.
So, even if the original documents have not been changed, Meilisearch will delete them to rewrite the same data with different internal IDs.
Changing settings should only reindex the data related to the changes.
This issue lists all the issues related to the diff-indexing subject.
TODO
P1:
Transform
when changing settings #4478SettingsDiff
structure and run extractions based on it #4480P2:
searchableAttributes
shouldn't trigger a reindexing #4484Transform
's disk usage when changing the settings #4485searchableAttribute
should not re-index all the attributes #4492P3:
Process
word-pair-proximity
database differently depending on the Settings #4482Modifying an embedder should not always recompute all the vectors #4615
Remove
facet
database when an attribute is removed from the facet list #4490Update the spec
Impacted teams
The text was updated successfully, but these errors were encountered: