The parse mode is being attached to the $query in a hard-coded way, using the 'terms' parse method with the default conjunction 'AND'. It is occurring at the highlighted lines here in IndexResource.php.
$parse_mode = $this->parseModeManager->createInstance('terms');
assert($parse_mode instanceof ParseModeInterface);
$query->setParseMode($parse_mode);
As a result, when performing a search with the terms "Navaho Sheep Herders", only documents that match all of these individual terms will be returned. While this behavior may be suitable for many projects, there are cases where search results are expected even if the documents match only one of the terms, such as "sheep" alone. This can be achieved by adjusting the parse mode to use the 'OR' operator as follows:
$parse_mode = $this->parseModeManager->createInstance('terms');
$parse_mode->setConjunction('OR');
assert($parse_mode instanceof ParseModeInterface);
$query->setParseMode($parse_mode);
I ended up patching the module to add the conjunction above in one of my projects.
This led to the following question:
Should the parse mode and its conjunction operator be configurable to provide greater flexibility in customizing the search behavior of this module?
Just use the module out of the box and conduct a search with some multi-word value "Lorem Ipsum".
Provide a configuration page to allow developers to select the parse mode plugin and the conjunction operator.
Review this proposal and implement it.
A new configuration page will be created.
No API changes.
No data model changes.
Active
1.0
Code
Good idea, if possible could the OR conjunction be supported via the search string, at the level of a particular search?
That way the client could specify the operator, such as "match all keywords" or "match any keyword" etc..
As a related note, it seems at the moment including a logical operator, such as "OR" in the search query fulltext parameter will return a bad request error.