![solr suggester tutorial solr suggester tutorial](https://1zrnlw1lz3wt1zcsci363i2d-wpengine.netdna-ssl.com/wp-content/uploads/2019/05/Jimi-Cropped-750x451.jpg)
In Drupal 8, both module's maintainers decided to team up and consolidate efforts behind Search API and Search API Solr. Search API Solr was much more flexible, pluggable, and configurable, but required more initial effort to set up. There were some efforts to consolidate things like schema configuration, so people would have an easier time switching between the two modules, but on the whole, the development efforts for Solr in Drupal 7 have been fragmented, so a lot of people (myself included) were torn between some of the benefits of each module and it's ecosystem.Īpache Solr Search provided a nicer out-of-the-box experience and required less configuration for standard search functionality. Unfortunately, having two separate modules and architectures meant many add-on features were developed twice. Both modules worked great in Drupal 7, and both provided many powerful features for modern search, like fast full-text search and indexing, search facets, and autocomplete. If you've ever used Apache Solr as a search engine for your Drupal site, you know there were two modules that could power search functionality: Apache Solr Search and Search API Solr. 6 to 7, or 7 to 8), they often take the time to rearchitect the module (and sometimes an entire related ecosystem of modules) to make development more efficient, clean up cruft, and improve current features. When module authors decide to port their modules to a new major version of Drupal (e.g.