Search API provides a very good trackers, filters and batch control for content entities. It makes sense to leverage that infrastructure instead of implementing redundant features.
Therefore we need to create a backend, only for indexing but not searching.

Comments

mkalkbrenner created an issue. See original summary.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Title: Provide a Seacrh API Backend » Provide a Search API Backend

  • mkalkbrenner committed cd55cc77 on 2.1.x 
    Issue #3467780 by mkalkbrenner: Provide a Search API Backend

  • mkalkbrenner committed 0ead53cf on 2.1.x 
    Issue #3467780 by mkalkbrenner: Provide a Search API Backend
mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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