Default processor config schema doesn't seem to work

Created on 13 April 2025, 12 days ago

Problem/Motivation

I created a new processor and my kernel test was failing with a schema error until I added

plugin.plugin_configuration.search_api_processor.pantheon_tags:
  type: search_api.fields_processor_configuration
  label: 'Pantheon tags processor configuration'

Steps to reproduce

Likely deleting the schema definition for plugin.plugin_configuration.search_api_processor.ignorecase should trigger this.

Proposed resolution

Probably delete the default as it is just not working. Who knows what's going on with config schema.

Remaining tasks

πŸ› Bug report
Status

Active

Version

1.0

Component

General code

Created by

πŸ‡¨πŸ‡¦Canada Charlie ChX Negyesi 🍁Canada

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Charlie ChX Negyesi
  • πŸ‡¦πŸ‡ΉAustria drunken monkey Vienna, Austria

    What exactly was the schema error. The default is search_api.default_processor_configuration, so if you needed to add search_api.fields_processor_configuration then maybe your processor inherits from FieldsProcessorPluginBase? In that case, it is expected that you would need to specify that explicitly, we have no way of detecting in the config schema whether a processor inherits from that.

    For those processors that just inherit from ProcessorPluginBase it seems to work fine. For instance, there is no explicit schema for the entity_status processor.

Production build 0.71.5 2024