Extend functionality support

Just wondering is Excerpt also supported? Does this require any extra configuration? Just adding the view in my issue, isn't resulting in anything.

Also a small maintainer ship, you can consider using Component to note what "part" of the system it touches (e.g. Search Api Integration) etc.

This is a field you can add in Views. Called " Search: Excerpt" it should show "were" in the result it found a relevant match with the query. In my install it never trows any data into this. Using the normal search api with database search, it does fill it.

Fixed it, it seems like the index wasn't properly picking up the text. Fixed it by clearing the indicie.

1) Would love to see http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/search-suggesters.html implemented. So that we can for example suggest other "terms" when a search trows no results.

2) This lists search_api_spellcheck support is yet to be developed, on the project page it is listed as being supported. Which one is correct? I also filed https://www.drupal.org/node/2314493 since it seems it doesn't even work anymore.

3) Implementing http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/analysis-snowball-analyzer.html should significantly improve the results. With an symphony example at http://richardmiller.co.uk/2011/11/18/symfony2-improving-elasticsearch-r... on how to implement this.

1) Doesn't seem to work for me, is there a special configuration that is required?

2) You are absolutely right about that. The summary confused me, I updated the summary of this issue.

3) That sounds good, I will follow that issue and test when possible.

Hi,

I'm using the Search Page to show the search results and I'm wondering if I could use the spellcheck feature with this specific module.

I was using Views at first but the highlighting wasn't working so I switched to Search Page and it's working fine. But I don't see how to integrate the spellcheck feature.

Thanks!

Edit:
***Found my solution in the Search Page module finally***

Checking on the status of these features in 2025...

1. search_api_grouping - this will be done in #2192597: Add support for search_api_grouping
2. search_api_multi -
   1. This feature was only supported in search_api-7.x-1.x, and no longer exists in search_api-8.x-1.x
   2. Neither search_api nor elasticsearch_connector have any supported Drupal 7 versions.
   3. As of 2025-08-30, there are ~251 sites still using a elasticsearch_connector-7.x version
   4. Is there still interest in adding support for this to an elasticsearch_connector-7.x version?
3. search_api_service_extra -
   1. This feature was only supported in search_api-7.x-1.x, and no longer exists in search_api-8.x-1.x
   2. Neither search_api nor elasticsearch_connector have any supported Drupal 7 versions.
   3. As of 2025-08-30, there are ~251 sites still using a elasticsearch_connector-7.x version
   4. Is there still interest in adding support for this to an elasticsearch_connector-7.x version?
4. search_api_data_type_location - this was added to elasticsearch_connector-7.x-1.x in #2192609: Elasticsearch Connector -> Search Api Integration -> Geo functionality, elasticsearch_connector-8.x-5.x in #2865662: Add support for geofield mapping, elasticsearch_connector-8.x-7.x in #3061167: ES 7.x support!, and still works in the elasticsearch_connector-8.0.x version
5. search_api_data_type_geohash -
   1. This appears to come from the Drupal 7 versions of the Geocluster module (it was never present in the Drupal 8 version), which no longer has any supported releases (and as of 2025-08-30, only 49 sites still use this module)
   2. Is there still interest in adding support for this to an elasticsearch_connector-7.x version?

Looking at the comments...

The request for Excerpt support from #2 and clarified in #5 was done in #3077596: Support Elasticsearch server highlighting

The request for Suggesters support in #7 and #11 was done in #3456387: Support for Search API Spellcheck

The request for custom analyzer support in #7 will be done in #2285797: Define custom analyzers for an index

Note also that support for "More Like This" queries (i.e.: search_api_mlt) was added in 8.0.x as part of #3270464: Investigate search_api_opensearch as base for elasticsearch_connector.

EDITED: While Elasticsearch 8 doesn't appear to natively support sorting randomly, it looks like a contributor has found a way to support Search API's search_api_random_sort feature in #3127445: Add support for search_api_random_sort.

Given that all the functionality requests that I can see in this ticket either...

1. has its own tracking tickets (#2192597: Add support for search_api_grouping, #2285797: Define custom analyzers for an index),
2. is done (#2192609: Elasticsearch Connector -> Search Api Integration -> Geo functionality et. al., #3077596: Support Elasticsearch server highlighting, #3456387: Support for Search API Spellcheck), or,
3. is only relevant for unsupported versions of Drupal core, or modules (search_api_multi, search_api_service_extra, search_api_data_type_geohash) and the maintainers need clarification on whether people still want it

... I'm going to mark this ticket as Postponed (maintainer needs more info) until we hear back!

(forgot to change the status before clicking Save on that last comment)

Added follow-up issues as related issues so they link back here.

From my comment in #12...

Given that all the functionality requests that I can see in this ticket either...

1. has its own tracking tickets (#2192597: Add support for search_api_grouping, #2285797: Define custom analyzers for an index),
2. is done (#2192609: Elasticsearch Connector -> Search Api Integration -> Geo functionality et. al., #3077596: Support Elasticsearch server highlighting, #3456387: Support for Search API Spellcheck), or,
3. is only relevant for unsupported versions of Drupal core, or modules (search_api_multi, search_api_service_extra, search_api_data_type_geohash) and the maintainers need clarification on whether people still want it

Given that I haven't heard otherwise in ~12 months, I'm going to move this issue to Fixed and grant credit.

Thank you to everyone who contributed, and thank you in advance for your understanding and patience with me as I try to make this module's issue queue more maintainable (i.e.: by closing issues that are fixed and/or covered elsewhere).