Search API allows contrib modules to define additional types which backends can optionally support. Those always need to specify a fallback type, such that backends which do not support that type can still index the field, albeit probably in a less than ideal fashion.

The database backend doesn’t properly check for a fallback type in several situations, instead just reporting an “unknown field type”.

Steps to reproduce

  1. Install some module with a new Search API field type.
  2. On an index that uses a server with a database backend, set a field’s type to that new field.
  3. This will lead to (logged) errors right away and then again (if you get that far) during indexing. No items can be indexed.

Comments

drunken monkey created an issue. See original summary.

drunken monkey’s picture

Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new7.25 KB
new9.12 KB

This should fix it.

drunken monkey’s picture

Ah, makes sense. Sorry, don’t have Postgres set up locally, currently.

  • drunken monkey committed 29f6bc7 on 8.x-1.x
    Issue #3258802 by drunken monkey: Fixed errors when indexing fields with...
drunken monkey’s picture

Status: Needs review » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.