Search call fails when views multi-valued exposed filter

Created on 16 June 2022, over 2 years ago

Updated 1 April 2024, 9 months ago

Problem/Motivation

When filtering through a multi-valued exposed filter in a search api view with an elastic index, no results appear and this message is displayed to the user:

Failed to make search call to http://localhost:9200/elasticsearch_index_d9_content_index/_search.
Elasticsearch response: [1:91] [terms_lookup] unknown field [1] [reason: [1:95] [bool] failed to parse field [filter]]

Steps to reproduce

1. Install search_api, elasticsearch_connector 8.0.x-dev
2. Create elasticsearch cluster, search api server and index with for example basic content configuration
3. Create some tags, articles, basic pages and index the content
4. Create a view with your elastic index and add term or content type exposed filter.
5. When exposed filter is single-value, the view works and results are ok
6. When exposed filter is multi-value, no results are displayed and the previous message appears.

Proposed resolution

Fix the error on elastic search query creation

Remaining tasks

User interface changes

None

API changes

None

Data model changes

None

🐛 Bug report

Status

Closed: outdated

Version

8.0

Component

Code

Created by

🇪🇸Spain budalokko Girona

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 9 months ago →
🇨🇦Canada mparker17 UTC-4
@budalokko and @KarimBou, we've made some big changes to the code in the 8.0.x-dev branch when we merged 📌 Investigate search_api_opensearch as base for elasticsearch_connector Fixed .

May we trouble you to try out the latest 8.0.x-dev release → and see if it fixes the problem that you reported here? If it does not, may we trouble you to change this issue's "Status" back to "Needs work"?

(I'm cleaning up issues in the 8.0.x-dev branch as part of a big review of open issues for 🌱 Plan for 8.0.0-alpha release Active : thank you for your patience with me!)
Status changed to Closed: outdated 9 months ago3:45pm 1 April 2024
Comment 9 months ago →
🇪🇸Spain budalokko Girona
@mparker17 thanks for your work on this module. This issue has been fixed in the mentioned latest 8.0.x-dev release.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024