Apply highlight on the best match of the field - disable highlight on stop-words

[curquiza]

Following this issue: meilisearch/meilisearch#4105

A solution could be to provide a setting not to highlight the stop words

[curquiza]

Pining @ManyTheFish to let you know

Is disabling highlight on stop-words something possible to do?

[abdullah-alnahas]

I think a good way to implement this is by introducing an additional parameter to specify whether or not to highlight stop words. This offers more flexibility than placing it in the settings. What do you think?

[curquiza]

@ManyTheFish I think I definitely do not understand something here. Not highlighting stop-words is already the by default Meilisarch behavior:

with stop words of and the

without any stop words

[abdullah-alnahas]

Not highlighting stop-words is the default behavior in Meilisearch.

@curquiza, do you need to update the stop words set (and add words like 'the') when you create a new index? Or is it populated with a default set for each language?

[curquiza]

You have to update your stop words yourself @abdullah-alnahas, Meilisearch will not add default stop-words depending on your dataset language

[ManyTheFish]

@curquiza, my bad, indeed the stop word are not highlighted, the highlighter doesn't get the stop words from the search query, they have been filtered before. This means that the stopword shouldn't be highlighted. It's seems to be a bug, sorry again it's my bad.
More precisely about the source of this behavior, I don't know why the "ال" is highlighted.

[curquiza]

@abdullah-alnahas can you described a little bit more your usage. What is problematic for you currently?
Is it the same issue than meilisearch/meilisearch#4105 or different?

We need to be sure adding the setting is the right solution to fix the issue

[abdullah-alnahas]

Yes, it is the same issue. As I replied above, perhaps introducing a parameter instead of a setting would offer more flexibility. What are your thoughts on this?

[curquiza]

Closing the discussion since it's not a feature request, but probably a bug. We will re-open a discussion later if needed, but the base of the discussion here are not good