Elasticsearch Connector Views integration

Created on 31 January 2016, over 8 years ago
Updated 17 July 2023, 11 months ago

Implement the 8.x Elasticsearch Connector Views integration after analysing in details the ability of Search API to fetch data from remote sources.
Elasticsearch Connector Views integration is one of the main used functionality in 7.x that should be available in 8.x with combination with facets and exposed filters.

✨ Feature request
Status

Needs review

Version

7.0

Component

Code

Created by

πŸ‡§πŸ‡¬Bulgaria lachezar.valchev

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

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡³πŸ‡±Netherlands ralphvdhoudt

    When using Contextual filters the ArgumentPluginBase add the field with the table alias even if no alias is used, resulting in a "." fieldname

    Added code to replace "." to ""

  • πŸ‡«πŸ‡·France Dakwamine

    @ralphvdhoudt I see a removed file in the interdiff of #19. Was it intentional?

  • πŸ‡«πŸ‡·France Dakwamine

    I made a side patch (i.e. use it on top of the base patch you are using) which fixes a bug about the date field views plugin, especially when a non timestamp value is indexed (like strict_date_optional_time). When not using this patch, views fails to render the results when a non timestamp date is offered to the views plugin.

    The patch worked on 8.x-7.0-alpha3 with the #13 base patch (it should work on other base patches).

  • πŸ‡«πŸ‡·France Dakwamine

    The attached patch is the #18 + the patch #19 made compatible with PHP7 (replaced str_starts_with with strpos).

  • πŸ‡«πŸ‡·France Dakwamine

    This one contains the fixes from #21 about the timestamp fields.

  • πŸ‡«πŸ‡·France Dakwamine

    This one is a fix over the field deduplication during the query building. Before, the deduplication resulted in ES returning an error about invalid string key. This happens when two fields of the same "source field" are retrieved, and only when they are not placed at the end of the field list, causing a "hole" in the index: key 0, key 1, key 2, key 4.

    By reindexing the array, it makes the query work again.

Production build 0.69.0 2024