You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Benoit Tellier (Jira)" <se...@james.apache.org> on 2022/05/05 04:13:00 UTC
[jira] [Closed] (JAMES-1882) ElasticSearch does not aggregate words researched
[ https://issues.apache.org/jira/browse/JAMES-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benoit Tellier closed JAMES-1882.
---------------------------------
Resolution: Won't Fix
This behaviour is expected from full text search.
Clients, by not precising sorts, can let the search engine sorts result by relevance.
> ElasticSearch does not aggregate words researched
> -------------------------------------------------
>
> Key: JAMES-1882
> URL: https://issues.apache.org/jira/browse/JAMES-1882
> Project: James Server
> Issue Type: Bug
> Components: JMAP
> Reporter: Laura Royet
> Assignee: Antoine Duprat
> Priority: Major
>
> Currently, when making a getMessageList request with a String FilterCondition containing several words separeted by white-spaces or hyphens, the message retrieved will not necessarily contain all the wanted words because basically ElasticSearch make a OR request.
> This does not comply with the JMAP specification.
> Example:
> When using ""OpenPaas anticonstitutionn" as a String FilterCondition, messages containing only "Openpaas" are retrieved.
> To solve this bug we can choose to implement AND in ElasticSearch (terms aggregation) or to amend the JMAP specification.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org