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
But when I remove a synonym from a department the department is still indexed via the previously removed synonym, although the updated entry does not contain any information about the previous relationship (debugged via transformEntry).
I was able to bypass this issue by creating a dynamic attribute in transformEntry (but I think it should also work by using the relationship data directly):
Hi @20x-dz I read your issue a couple of times. It was hard to decouple it from the similarity of #424.
Could you please provide a reproducible case? It makes it easier to help you with that. A failing test case would be even better. Although our time is very short to do the fixes ourselves, we are a small team that maintains more than 20 different types of integrations, so we rely on the community's power to help improve those repositories.
I'll mark this as needs investigation, so if someone could join and provide a PR, it would be more than amazing.
Hope you will understand, and thank you very much for using Meilisearch ❤️
Description
The content of deleted relations that are being used as
searchableAttributes
are still kept in the index.Assume the following model (simplified):
To be able to expand the search results I created a
SearchSynonm
model with a n:m relationship withDepartment
(and other models).Searching for a department with a previously created and attached searchSynonym works just fine with the following setting (simplified):
But when I remove a synonym from a department the department is still indexed via the previously removed synonym, although the updated entry does not contain any information about the previous relationship (debugged via
transformEntry
).I was able to bypass this issue by creating a dynamic attribute in
transformEntry
(but I think it should also work by using the relationship data directly):Updating the index through the strapi settings works as well.
Note: I am fully aware of #424, but this is a different issue, as the indexed model is not being updated accordingly when modified.
Assume the following query for the next two points:
Expected behavior
A search should not return entries that had a searchable relationship removed.
Current behavior
Data in the index is not being updated.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: