Loading...
 
Skip to main content

Elastic search should ignore stopwords on ''exact'' searches

  • Tracker item actions
Trackers
Items
Status
Open
Subject
Elastic search should ignore stopwords on ''exact'' searches
Version
21.x
Category
  • Bug
Feature
Search
Resolution status
New
Submitted by
Jean-Marc Libs
Lastmod by
Jean-Marc Libs
Rating
(0)
Description

If I want to look up all users which are waiting for the admin to validate them, I can do this LIST plugin:

Copy to clipboard
{LIST()}
  {filter field="object_type" exact="user" }
  {filter field="waiting" exact="a" }
  {pagination max="9999"}
{LIST}


This works fine using unified search with option mysql fulltext search.

Using option Elastic search nothing is returned because "a" is in the stopwords list. Removing "a" from the stopwords list fixes the issue.

I can understand why stopwords are stripped from searches such as content="something". That's the idea of stopwords.
But on exact searches stopwords should not be stripped. Because, by the definition of "exact search", one knows exactly what one is searching for.

Also, we should not get different results depending on the unified search option.

Importance
10 high
Easy to solve?
5
Priority
50
Demonstrate Bug on Tiki 19+
Demonstrate Bug (older Tiki versions)
Ticket ID
7707
Created
Thursday 25 March, 2021 01:24:58 UTC
by Jean-Marc Libs
LastModif
Thursday 25 March, 2021 01:24:58 UTC


Show PHP error messages