Support setting parse mode and conjunction for fulltext conditions

Created on 7 August 2018, over 6 years ago

Updated 9 July 2024, 4 months ago

It 's possible to configure multiple exposed fulltext search boxes.

Depending on the concrete configuration, Search API mixes the entered words as keys or passes the second (third, fourth) search box user input as conditions of the query.

A query can only have one parse mode. But it's possible to configure different parse modes for each fulltext search box in Views. Somehow, Search API picks one of them. Depending on this parse mode and the user input you can run into no results, or even worse Solr exceptions.

I see two different solutions:

Set parse mode on query for keys and optionally on each Condition
Ensure that all exposed fulltext filters in one View share the same parse mode

The second option might be easier to achieve but there're use-cases for the first one.

✨ Feature request

Status

Active

Version

1.0

Component

Views integration

Created by

🇩🇪Germany mkalkbrenner 🇩🇪

Live updates comments and jobs are added and updated live.

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment almost 2 years ago →
🇬🇧United Kingdom robcarr Perthshire, Scotland
I'm not sure if there has been any movement on this.

I'm currently unable to utilise search_api_spellcheck with a large Fulltext index.

InvalidArgumentException: The selected parse mode for fulltext fields is not compatible to Search API Spellcheck
Comment 4 months ago →
🇪🇸Spain tuwebo
Thinking about this issue,
Maybe we could use the Boolean Query parser to run both queries and this way combining them. I have never used it, but ti looks like it could be done. I am thinking about something like (didn't test it):
q={!bool}must=({!lucene}field1:value1) must=({!edismax qf=field2^2}value2)

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024