- Issue created by @admirlju
I have an idea why this happens. It comes down to
getBackendDefinedFields
method in the backend. This is used to expose fixed fields to views, in our case these special fields aren't fixed so they don't have path mapping, and none of them should be available to the view.I'd personally go with the simplest solution and just return an empty array. Since really these fields can be accessed using other fields. Or we can add fixed fields that map to these. I personally don't see the point in this second solution, but opinions are welcome.
- Merge request !44Issue #3396022: Error when indexing special fields (search_api_*) โ (Merged) created by admirlju
- Status changed to Needs review
about 1 year ago 8:00am 24 October 2023 Now we create the fields when calling the
getBackendDefiniedFields
method. So the error above does not show up and the already existing tests pass. Needs review.- ๐ฏ๐ตJapan hktang
I applied the patch to our site with meilisearch @2.0.0 and the message is gone. No more warnings. Thank you!
- ๐ฆ๐นAustria tgoeg
I also get "attribute
search_api_datasource
is not filterable" when I- create an index
- also use "node grants" in the filters (in hope of not indexing e.g. unpublished content)
- search as an anonymous user
It's hard to tell for me whether this is related? Or shall I raise a separate issue?
- ๐ฌ๐งUnited Kingdom Hephaestus
Can also confirm that the MR resolves the errors for us, with no obvious side effects.
-
bcizej โ
committed bbc43806 on 2.x authored by
admirlju โ
Issue #3396022 by admirlju, hktang, tgoeg, Hephaestus: Error when...
-
bcizej โ
committed bbc43806 on 2.x authored by
admirlju โ
- Status changed to Fixed
10 months ago 4:50pm 25 January 2024 Automatically closed - issue fixed for 2 weeks with no activity.